irq.h 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586
  1. /*
  2. * Copyright 2010 Tilera Corporation. All Rights Reserved.
  3. *
  4. * This program is free software; you can redistribute it and/or
  5. * modify it under the terms of the GNU General Public License
  6. * as published by the Free Software Foundation, version 2.
  7. *
  8. * This program is distributed in the hope that it will be useful, but
  9. * WITHOUT ANY WARRANTY; without even the implied warranty of
  10. * MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, GOOD TITLE or
  11. * NON INFRINGEMENT. See the GNU General Public License for
  12. * more details.
  13. */
  14. #ifndef _ASM_TILE_IRQ_H
  15. #define _ASM_TILE_IRQ_H
  16. #include <linux/hardirq.h>
  17. /* The hypervisor interface provides 32 IRQs. */
  18. #define NR_IRQS 32
  19. /* IRQ numbers used for linux IPIs. */
  20. #define IRQ_RESCHEDULE 0
  21. /* Interrupts for dynamic allocation start at 1. Let the core allocate irq0 */
  22. #define NR_IRQS_LEGACY 1
  23. #define irq_canonicalize(irq) (irq)
  24. void ack_bad_irq(unsigned int irq);
  25. /*
  26. * Different ways of handling interrupts. Tile interrupts are always
  27. * per-cpu; there is no global interrupt controller to implement
  28. * enable/disable. Most onboard devices can send their interrupts to
  29. * many tiles at the same time, and Tile-specific drivers know how to
  30. * deal with this.
  31. *
  32. * However, generic devices (usually PCIE based, sometimes GPIO)
  33. * expect that interrupts will fire on a single core at a time and
  34. * that the irq can be enabled or disabled from any core at any time.
  35. * We implement this by directing such interrupts to a single core.
  36. *
  37. * One added wrinkle is that PCI interrupts can be either
  38. * hardware-cleared (legacy interrupts) or software cleared (MSI).
  39. * Other generic device systems (GPIO) are always software-cleared.
  40. *
  41. * The enums below are used by drivers for onboard devices, including
  42. * the internals of PCI root complex and GPIO. They allow the driver
  43. * to tell the generic irq code what kind of interrupt is mapped to a
  44. * particular IRQ number.
  45. */
  46. enum {
  47. /* per-cpu interrupt; use enable/disable_percpu_irq() to mask */
  48. TILE_IRQ_PERCPU,
  49. /* global interrupt, hardware responsible for clearing. */
  50. TILE_IRQ_HW_CLEAR,
  51. /* global interrupt, software responsible for clearing. */
  52. TILE_IRQ_SW_CLEAR,
  53. };
  54. /*
  55. * Paravirtualized drivers should call this when they dynamically
  56. * allocate a new IRQ or discover an IRQ that was pre-allocated by the
  57. * hypervisor for use with their particular device. This gives the
  58. * IRQ subsystem an opportunity to do interrupt-type-specific
  59. * initialization.
  60. *
  61. * ISSUE: We should modify this API so that registering anything
  62. * except percpu interrupts also requires providing callback methods
  63. * for enabling and disabling the interrupt. This would allow the
  64. * generic IRQ code to proxy enable/disable_irq() calls back into the
  65. * PCI subsystem, which in turn could enable or disable the interrupt
  66. * at the PCI shim.
  67. */
  68. void tile_irq_activate(unsigned int irq, int tile_irq_type);
  69. void setup_irq_regs(void);
  70. #ifdef __tilegx__
  71. void arch_trigger_all_cpu_backtrace(bool self);
  72. #define arch_trigger_all_cpu_backtrace arch_trigger_all_cpu_backtrace
  73. #endif
  74. #endif /* _ASM_TILE_IRQ_H */