blob: f80f8ceabc67abd6ef57fce76cb1a224f53204c8 [file] [log] [blame]
Chris Metcalf867e3592010-05-28 23:09:12 -04001/*
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
15#ifndef _ASM_TILE_IRQ_H
16#define _ASM_TILE_IRQ_H
17
18#include <linux/hardirq.h>
19
20/* The hypervisor interface provides 32 IRQs. */
21#define NR_IRQS 32
22
23/* IRQ numbers used for linux IPIs. */
24#define IRQ_RESCHEDULE 1
25
Chris Metcalf28d71742011-05-02 16:06:42 -040026#define irq_canonicalize(irq) (irq)
27
Chris Metcalf867e3592010-05-28 23:09:12 -040028void ack_bad_irq(unsigned int irq);
29
30/*
Chris Metcalffb702b92010-06-25 16:41:11 -040031 * Different ways of handling interrupts. Tile interrupts are always
32 * per-cpu; there is no global interrupt controller to implement
33 * enable/disable. Most onboard devices can send their interrupts to
34 * many tiles at the same time, and Tile-specific drivers know how to
35 * deal with this.
36 *
37 * However, generic devices (usually PCIE based, sometimes GPIO)
38 * expect that interrupts will fire on a single core at a time and
39 * that the irq can be enabled or disabled from any core at any time.
40 * We implement this by directing such interrupts to a single core.
41 *
42 * One added wrinkle is that PCI interrupts can be either
43 * hardware-cleared (legacy interrupts) or software cleared (MSI).
44 * Other generic device systems (GPIO) are always software-cleared.
45 *
46 * The enums below are used by drivers for onboard devices, including
47 * the internals of PCI root complex and GPIO. They allow the driver
48 * to tell the generic irq code what kind of interrupt is mapped to a
49 * particular IRQ number.
Chris Metcalf867e3592010-05-28 23:09:12 -040050 */
Chris Metcalffb702b92010-06-25 16:41:11 -040051enum {
52 /* per-cpu interrupt; use enable/disable_percpu_irq() to mask */
53 TILE_IRQ_PERCPU,
54 /* global interrupt, hardware responsible for clearing. */
55 TILE_IRQ_HW_CLEAR,
56 /* global interrupt, software responsible for clearing. */
57 TILE_IRQ_SW_CLEAR,
58};
59
60
61/*
62 * Paravirtualized drivers should call this when they dynamically
63 * allocate a new IRQ or discover an IRQ that was pre-allocated by the
64 * hypervisor for use with their particular device. This gives the
65 * IRQ subsystem an opportunity to do interrupt-type-specific
66 * initialization.
67 *
68 * ISSUE: We should modify this API so that registering anything
69 * except percpu interrupts also requires providing callback methods
70 * for enabling and disabling the interrupt. This would allow the
71 * generic IRQ code to proxy enable/disable_irq() calls back into the
72 * PCI subsystem, which in turn could enable or disable the interrupt
73 * at the PCI shim.
74 */
75void tile_irq_activate(unsigned int irq, int tile_irq_type);
76
Chris Metcalffb702b92010-06-25 16:41:11 -040077void setup_irq_regs(void);
Chris Metcalf867e3592010-05-28 23:09:12 -040078
79#endif /* _ASM_TILE_IRQ_H */