Home
last modified time | relevance | path

Searched refs:IRQ (Results 1 – 200 of 429) sorted by relevance

123

/linux-4.4.14/Documentation/arm/
DInterrupts14 Secondly, the IRQ subsystem.
37 SA1111 IRQ handler, SA1111 IRQs can hold off SMC9196 IRQs indefinitely.
46 We also bring the idea of an IRQ "chip" (mainly to reduce the size of
55 * Acknowledge the IRQ.
56 * If this is a level-based IRQ, then it is expected to mask the IRQ
61 * Mask the IRQ in hardware.
65 * Unmask the IRQ in hardware.
69 * Re-run the IRQ
73 * Set the type of the IRQ.
84 the hardware IRQ if possible. If not, may call the handler
[all …]
DNetwinder47 IRQ type Description
/linux-4.4.14/Documentation/zh_CN/
DIRQ.txt1 Chinese translated version of Documentation/IRQ.txt
12 Documentation/IRQ.txt 的中文翻译
25 何为 IRQ?
27 一个 IRQ 是来自某个设备的一个中断请求。目前，它们可以来自一个硬件引脚，
28 或来自一个数据包。多个设备可能连接到同个硬件引脚，从而共享一个 IRQ。
30 一个 IRQ 编号是用于告知硬件中断源的内核标识。通常情况下，这是一个
34 一个 IRQ 编号是设备上某个可能的中断源的枚举。通常情况下，枚举的编号是
38 架构可以对 IRQ 编号指定额外的含义，在硬件涉及任何手工配置的情况下，
39 是被提倡的。ISA 的 IRQ 是一个分配这类额外含义的典型例子。
Dgpio.txt61 - 输入通常可作为 IRQ 信号,一般是沿触发,但有时是电平触发。这样的 IRQ
194 休眠，这不能在 IRQ 例程(中断上下文)中执行。
210 访问这样的 GPIO 需要一个允许休眠的上下文，例如线程 IRQ 处理例程，并用以上的
213 除了这些访问函数可能休眠，且它们操作的 GPIO 不能在硬件 IRQ 处理例程中访问的
358 GPIO 映射到 IRQ
360 GPIO 编号是无符号整数;IRQ 编号也是。这些构成了两个逻辑上不同的命名空间
361 (GPIO 0 不一定使用 IRQ 0)。你可以通过以下函数在它们之间实现映射:
363 /* 映射 GPIO 编号到 IRQ 编号 */
366 /* 映射 IRQ 编号到 GPIO 编号 (尽量避免使用) */
370 (例如,某些 GPIO 无法做为 IRQ 使用。)以下的编号错误是未经检测的:使用一个
[all …]
/linux-4.4.14/Documentation/
DIRQ-domain.txt4 space where each separate IRQ source is assigned a different number.
8 IRQ numbers.
13 mechanisms as the IRQ core system by modelling their interrupt
17 hardware interrupt numbers: whereas in the past, IRQ numbers could
18 be chosen so they matched the hardware IRQ line into the root
23 interrupt numbers, called hardware irq's, from Linux IRQ numbers.
27 the controller-local IRQ (hwirq) number into the Linux IRQ number
30 The irq_domain library adds mapping between hwirq and IRQ numbers on
37 be easily extended to support other IRQ topology data sources.
47 between hwirq and IRQ numbers. Mappings are added to the irq_domain
[all …]
DIRQ.txt1 What is an IRQ?
3 An IRQ is an interrupt request from a device.
6 sharing an IRQ.
8 An IRQ number is a kernel identifier used to talk about a hardware
13 An IRQ number is an enumeration of the possible interrupt sources on a
19 Architectures can assign additional meaning to the IRQ numbers, and
DIRQ-affinity.txt5 SMP IRQ affinity
7 /proc/irq/IRQ#/smp_affinity and /proc/irq/IRQ#/smp_affinity_list specify
8 which target CPUs are permitted for a given IRQ source. It's a bitmask
10 allowed to turn off all CPUs, and if an IRQ controller does not support
11 IRQ affinity then the value will not change from the default of all cpus.
14 to all non-active IRQs. Once IRQ is allocated/activated its affinity bitmask
40 Now lets restrict that IRQ to CPU(4-7).
Dmen-chameleon-bus.txt36 that only use a single memory resource and share the PCI legacy IRQ. Not
41 - A per-carrier IRQ domain for carrier devices that have one (or more) IRQs
66 properties of the carrier device (like querying the IRQ number of a PCI
71 query for the IRQ number the device should use.
86 The current implementation assigns exactly one memory and one IRQ resource
98 Each MCB device has exactly one IRQ resource, which can be requested from the
100 method, the IRQ number assigned by the carrier device will be returned,
101 otherwise the IRQ number inside the Chameleon table will be returned. This
Dparport.txt9 because there are a lot of people using the same IRQ for their
30 0x3bc with no IRQ, one at 0x378 using IRQ 7, and one at 0x278 with an
31 auto-detected IRQ. Currently, PC-style (parport_pc), Sun `bpp',
82 command-line will make parport use any IRQ lines or DMA channels that
146 irq Parallel port's IRQ, or -1 if none is being used.
165 advantage of COMPAT and ECP modes if it has an IRQ
223 * IRQ autoprobing works only for a few port types at the moment.
Drtc.txt30 IRQ, so they can't all issue alarms; and where standard PC RTCs can
49 are reported by interrupt number 8. (Oh! So *that* is what IRQ 8 is
50 for...) It can also function as a 24hr alarm, raising IRQ 8 when the
76 occasional interrupt pileup (i.e. > 1 IRQ event since last read) for
175 is connected to an IRQ line, it can often issue an alarm IRQ up to
180 setting the longer alarm time and enabling its IRQ using a single
Dirqflags-tracing.txt1 IRQ-flags state tracing
14 are locking APIs that are not used in IRQ context. (the one exception
Dmailbox.txt26 by the remote by getting an IRQ or polling some hardware flag
28 The method in order of preference is IRQ -> Poll -> None, which
/linux-4.4.14/Documentation/gpio/
Ddriver.txt46 - method to return the IRQ number associated to a given GPIO
68 on -RT (inside hard IRQ handlers and similar contexts). Normally this should
77 The IRQ portions of the GPIO block are implemented using an irqchip, using
91 an SoC. This means that there is a fast IRQ handler for the GPIOs that
92 gets called in a chain from the parent IRQ handler, most typically the
108 RT_FULL: Note, chained IRQ handlers will not be forced threaded on -RT.
110 in chained IRQ handler.
112 - chained IRQ handler can be converted to generic irq handler and this way
113 it will be threaded IRQ handler on -RT and hard IRQ handler on non-RT
115 Know W/A: The generic_handle_irq() is expected to be called with IRQ disabled,
[all …]
Dconsumer.txt175 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ
200 sleeping, which can't be done from inside IRQ handlers.
213 IRQ handler, and those accessors must be used instead of spinlock-safe
324 GPIO lines can quite often be used as IRQs. You can get the IRQ number
329 It will return an IRQ number, or a negative errno code if the mapping can't be
330 done (most likely because that particular GPIO cannot be used as IRQ). It is an
332 gpiod_direction_input(), or to use an IRQ number that didn't originally come
336 free_irq(). They will often be stored into IRQ resources for platform devices,
337 by the board-specific initialization code. Note that IRQ trigger options are
338 part of the IRQ interface, e.g. IRQF_TRIGGER_FALLING, as are system wakeup
Dgpio-legacy.txt40 - Inputs can often be used as IRQ signals, often edge triggered but
164 (nonthreaded) IRQ handlers and similar contexts.
200 This requires sleeping, which can't be done from inside IRQ handlers.
218 a threaded IRQ handler, and those accessors must be used instead of
381 GPIO numbers are unsigned integers; so are IRQ numbers. These make up
382 two logically distinct namespaces (GPIO 0 need not use IRQ 0). You can
385 /* map GPIO numbers to IRQ numbers */
388 /* map IRQ numbers to GPIO numbers (avoid using this) */
395 to use an IRQ number that didn't originally come from gpio_to_irq().
401 or free_irq(). They will often be stored into IRQ resources for platform
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Darm,versatile-fpga-irq.txt3 One or more FPGA IRQ controllers can be synthesized in an ARM reference board
5 controllers are OR:ed together and fed to the CPU tile's IRQ input. Each
12 as the FPGA IRQ controller has no configuration options for interrupt
34 - interrupts: if the FPGA IRQ controller is cascaded, i.e. if its IRQ
35 output is simply connected to the input of another IRQ controller,
36 then the parent IRQ shall be specified in this property.
Dcdns,xtensa-pic.txt8 When it's 1, the first cell is the internal IRQ number.
9 When it's 2, the first cell is the IRQ number, and the second cell
11 Periferals are usually connected to a fixed external IRQ, but for different
12 core variants it may be mapped to different internal IRQ.
13 IRQ sensitivity and priority are fixed for each core variant and may not be
Dti,keystone-irq.txt1 Keystone 2 IRQ controller IP
4 host using the IRQ controller IP. It provides 28 IRQ signals to ARM.
5 The IRQ handler running on HOST OS can identify DSP signal source by
Dsnps,archs-idu-intc.txt4 dynamic IRQ routing, load balancing of common/external IRQs towards core intc.
14 First cell specifies the "common" IRQ from peripheral to IDU
45 interrupts = <0 0>; /* upstream idu IRQ #24, Round Robin */
Dbrcm,bcm7038-l1-intc.txt9 - 64, 96, 128, or 160 incoming level IRQ lines
37 system, the driver will allow IRQ SMP affinity to be set up through the
Dbrcm,bcm2835-armctrl-ic.txt21 The 1st cell is the interrupt bank; 0 for interrupts in the "IRQ basic
22 pending" register, or 1/2 respectively for interrupts in the "IRQ pending
Dsnps,arc700-intc.txt12 Single Cell "interrupts" property of a device specifies the IRQ number
Dsnps,archs-intc.txt9 Single Cell "interrupts" property of a device specifies the IRQ number
Dti,omap-intc-irq.txt4 96 or 128 IRQ signals to the ARM host depending on the SoC.
Dallwinner,sun67i-sc-nmi.txt11 interrupt source. The value shall be 2. The first cell is the IRQ number, the
Dnxp,lpc3220-mic.txt9 The first cell is the IRQ number
Dst,sti-irq-syscfg.txt14 - st,syscfg : Phandle to Cortex-A9 IRQ system config registers
Datmel,aic.txt9 The first cell is the IRQ number (aka "Peripheral IDentifier" on datasheet).
Dqca,ath79-cpu-intc.txt3 On most SoC the IRQ controller need to flush the DDR FIFO before running
Dmarvell,armada-370-xp-mpic.txt10 The cell is the IRQ number
/linux-4.4.14/Documentation/ia64/
DIRQ-redir.txt1 IRQ affinity on IA64 platforms
6 By writing to /proc/irq/IRQ#/smp_affinity the interrupt routing can be
8 that described in Documentation/IRQ-affinity.txt for i386 systems.
11 IRQ target is one particular CPU and cannot be a mask of several
25 Set the default route for IRQ number 41 to CPU 6 in lowest priority
30 cat /proc/irq/IRQ#/smp_affinity
40 If the platform features IRQ redirection (info provided by SAL) all
44 for the IRQ routing. Currently in Linux XTP registers can have three
49 The IRQ is routed to the CPU with lowest XTP register value, the
65 For systems like the NEC AzusA we get IRQ node-affinity for free. This
/linux-4.4.14/arch/sh/boards/mach-microdev/
Dirq.c44 # error Inconsistancy in defining the IRQ# for Keyboard!
48 # error Inconsistancy in defining the IRQ# for Ethernet!
52 # error Inconsistancy in defining the IRQ# for USB!
56 # error Inconsistancy in defining the IRQ# for PS/2 Mouse!
60 # error Inconsistancy in defining the IRQ# for secondary IDE!
64 # error Inconsistancy in defining the IRQ# for primary IDE!
/linux-4.4.14/arch/blackfin/mach-bf548/
DKconfig189 int "IRQ MXVR Data"
294 int "IRQ Handshake DMA Status"
297 int "IRQ PIXC IN0"
300 int "IRQ PIXC IN1"
303 int "IRQ PIXC OUT"
306 int "IRQ SDH"
309 int "IRQ CNT"
312 int "IRQ KEY"
315 int "IRQ CAN1 RX"
327 int "IRQ USB INT0"
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
Disil,isl12057.txt10 and 2120 ARM-based NAS); On those devices, the IRQ#2 pin of the chip
15 be set when the IRQ#2 pin of the chip is not connected to the SoC but
26 the availability of an IRQ line connected to the SoC.
30 of the SoC connected to IRQ#2 of the RTC chip.
33 Example isl12057 node without IRQ#2 pin connected (no alarm support):
41 Example isl12057 node with IRQ#2 pin connected to main SoC via MPP6 (note
44 SoC, and the main function of the MPP used as IRQ line, i.e.
71 Example isl12057 node without IRQ#2 pin connected to the SoC but to a
Dxlnx-rtc.txt4 Separate IRQ lines for seconds and alarm
10 - interrupts: IRQ lines for the RTC.
Dorion-rtc.txt10 - interrupts: IRQ line for the RTC.
Dsunxi-rtc.txt9 - interrupts: IRQ line for the RTC.
Dsun6i-rtc.txt9 - interrupts : IRQ lines for the RTC alarm 0 and alarm 1, in that order.
Dxgene-rtc.txt9 - interrupts: IRQ line for the RTC.
Darmada-380-rtc.txt13 - interrupts: IRQ line for the RTC.
Drtc-mxc.txt9 - interrupts: IRQ line for the RTC.
Ddw-apb.txt10 - interrupts: IRQ line for the timer.
/linux-4.4.14/Documentation/power/
Dsuspend-and-interrupts.txt41 The IRQF_NO_SUSPEND flag is used to indicate that to the IRQ subsystem when
43 leave the corresponding IRQ enabled so as to allow the interrupt to work as
48 Note that the IRQF_NO_SUSPEND flag affects the entire IRQ and not just one
49 user of it. Thus, if the IRQ is shared, all of the interrupt handlers installed
52 the IRQ's users. For this reason, using IRQF_NO_SUSPEND and IRQF_SHARED at the
73 The IRQ subsystem provides two helper functions to be used by device drivers for
75 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
78 Calling enable_irq_wake() causes suspend_device_irqs() to treat the given IRQ
79 in a special way. Namely, the IRQ remains enabled, by on the first interrupt
103 IRQ subsystem to trigger a system wakeup.
[all …]
/linux-4.4.14/drivers/pinctrl/sh-pfc/
Dpfc-r8a73a4.c252 #define IRQ(a) IRQ##a##_MARK macro
254 F1(LCDD0), F3(PDM2_CLK_0), F7(DU0_DR0), IRQ(0), /* Port0 */ enumerator
255 F1(LCDD1), F3(PDM2_DATA_1), F7(DU0_DR19), IRQ(1), enumerator
256 F1(LCDD2), F3(PDM3_CLK_2), F7(DU0_DR2), IRQ(2), enumerator
257 F1(LCDD3), F3(PDM3_DATA_3), F7(DU0_DR3), IRQ(3), enumerator
258 F1(LCDD4), F3(PDM4_CLK_4), F7(DU0_DR4), IRQ(4), enumerator
259 F1(LCDD5), F3(PDM4_DATA_5), F7(DU0_DR5), IRQ(5), enumerator
260 F1(LCDD6), F3(PDM0_OUTCLK_6), F7(DU0_DR6), IRQ(6), enumerator
261 F1(LCDD7), F3(PDM0_OUTDATA_7), F7(DU0_DR7), IRQ(7), enumerator
262 F1(LCDD8), F3(PDM1_OUTCLK_8), F7(DU0_DG0), IRQ(8), enumerator
[all …]
/linux-4.4.14/Documentation/virtual/kvm/devices/
Dmpic.txt29 IRQ input line for each standard openpic source. 0 is inactive and 1
36 "attr" is the IRQ number. IRQ numbers for standard sources are the
39 IRQ Routing:
41 The MPIC emulation supports IRQ routing. Only a single MPIC device can
53 Access to non-SRC interrupts is not implemented through IRQ routing mechanisms.
/linux-4.4.14/Documentation/devicetree/bindings/crypto/
Dfsl-dcp.txt6 - interrupts : Should contain MXS DCP interrupt numbers, VMI IRQ and DCP IRQ
7 must be supplied, optionally Secure IRQ can be present, but
Datmel-crypto.txt10 - interrupts: Should contain the IRQ line for the AES.
30 - interrupts: Should contain the IRQ line for the TDES.
53 - interrupts: Should contain the IRQ line for the SHA.
Dsun4i-ss.txt6 - interrupts: Should contain the IRQ line for the Security System.
Dimg-hash.txt10 - interrupts : The designated IRQ line for the hashing module.
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-dsp-keystone.txt4 the DSP GPIO controller IP. It provides 28 IRQ signals per each DSP core.
12 - setting GPIO value to 1 causes IRQ generation on target DSP core;
13 - reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still
D8xxx_gpio.txt30 - interrupts: Interrupt mapping for GPIO IRQ.
35 module as an IRQ controller.
67 Example of a peripheral using the GPIO module as an IRQ controller:
Dgpio-xilinx.txt5 input/output/tristate. Both channels share the same global IRQ but
16 - interrupts : Interrupt mapping for GPIO IRQ.
Dpl061-gpio.txt9 - interrupts : Interrupt mapping for GPIO IRQ.
Dzx296702-gpio.txt9 - interrupts : Interrupt mapping for GPIO IRQ.
Dgpio-xgene-sb.txt6 only GPIO_DS8..GPIO_DS13 support interrupts. The IRQ mapping
Dgpio-altera.txt17 used has IRQ enabled as the interrupt type is not software controlled,
/linux-4.4.14/Documentation/x86/i386/
DIO-APIC.txt9 distribute IRQ load further.
34 none of those IRQ sources is performance-critical.
38 you can use the pirq= boot parameter to 'hand-construct' IRQ entries. This
46 connected to the PCI chipset IRQ routing facility (the incoming PIRQ1-4
59 Every PCI card emits a PCI IRQ, which can be INTA, INTB, INTC or INTD:
73 a card in slot4, issuing INTA IRQ, it will end up as a signal on PIRQ4 of
75 between the PIRQ lines. (distributing IRQ sources properly is not a
97 [value '0' is a generic 'placeholder', reserved for empty (or non-IRQ emitting)
101 permute all IRQ numbers properly ... it will take some time though. An
/linux-4.4.14/arch/arc/kernel/
Dentry-compact.S135 ;##################### Scratch Mem for IRQ stack switching #############
169 ; if L2 IRQ interrupted a L1 ISR, disable preemption
172 ; -L1 IRQ taken
174 ; -preemption off IRQ, user task in syscall picked to run
187 bbit0 r9, STATUS_A1_BIT, 1f ; L1 not active when L2 IRQ, so normal
338 ; Restore the saved sys context (common exit-path for EXCPN/IRQ/Trap)
339 ; IRQ shd definitely not happen between now and rtie
349 ; use the same priorty as rtie: EXCPN, L2 IRQ, L1 IRQ, None
372 ; if L2 IRQ interrupted an L1 ISR, we'd disabled preemption earlier
379 bbit0 r9, STATUS_A1_BIT, 149f ; L1 not active when L2 IRQ, so normal
Dentry-arcv2.S166 ; Restore the saved sys context (common exit-path for EXCPN/IRQ/Trap)
167 ; IRQ shd definitely not happen between now and rtie
184 ; Handle special case #1: (Entry via Exception, Return via IRQ)
209 ; Handle special case #2: (Entry via Exception in Delay Slot, Return via IRQ)
212 ; (since IRQ NOT allowed in DS in ARCv2, this can only happen if orig
215 ; IRQ RTIE won't reliably restore DE bit and/or BTA, needs workaround
Dentry.S295 ; interim IRQ).
317 ; Normal Trap/IRQ entry only saves Scratch (caller-saved) regs
369 ; preempt_schedule_irq() always returns with IRQ disabled
/linux-4.4.14/drivers/isdn/hisax/
DKconfig98 non-standard IRQ/port/shmem settings.
108 non-standard IRQ/port settings.
132 non-standard IRQ/port settings.
155 non-standard IRQ/port settings.
165 non-standard IRQ/port settings.
175 non-standard IRQ/port settings.
186 non-standard IRQ/port settings.
196 non-standard IRQ/port settings.
207 non-standard IRQ/port settings.
216 non-standard IRQ/port settings.
[all …]
/linux-4.4.14/arch/avr32/mach-at32ap/
Dat32ap700x.c48 #define IRQ(num) \ macro
608 IRQ(2),
622 IRQ(20),
631 IRQ(21),
648 IRQ(19),
757 IRQ(22),
769 IRQ(23),
785 IRQ(13),
792 IRQ(14),
799 IRQ(15),
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/bus/
Dbrcm,bus-axi.txt11 Automatic detection of the IRQ number is not working on
12 BCM47xx/BCM53xx ARM SoCs. To assign IRQ numbers to the cores, provide
14 IRQ used by the devices on the bus. The first address is just an index,
19 detected (e.g. IRQ numbers). Also some of the cores may be responsible
/linux-4.4.14/Documentation/devicetree/bindings/iio/accel/
Dlis302.txt36 - st,irq{1,2}-disable: disable IRQ 1/2
37 - st,irq{1,2}-ff-wu-1: raise IRQ 1/2 on FF_WU_1 condition
38 - st,irq{1,2}-ff-wu-2: raise IRQ 1/2 on FF_WU_2 condition
39 - st,irq{1,2}-data-ready: raise IRQ 1/2 on data ready contition
40 - st,irq{1,2}-click: raise IRQ 1/2 on click condition
41 - st,irq-open-drain: consider IRQ lines open-drain
42 - st,irq-active-low: make IRQ lines active low
Dmma8452.txt15 - interrupts: interrupt mapping for GPIO IRQ
Dbma180.txt15 - interrupts : interrupt mapping for GPIO IRQ, it should by configured with
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dbfticu.txt10 - interrupts: the main IRQ line to signal the collected IRQs
13 - interrupt-parent: the parent IRQ ctrl the main IRQ is connected to
Dmax8925.txt6 - interrupts : IRQ line for the max8925 chip
10 - The cell is the max8925 local IRQ number
13 - maxim,tsc-irq: there are 2 IRQ lines for max8925, one is indicated in
Dda9055.txt27 - interrupts: IRQ line info for da9055 chip.
28 - interrupt-controller: da9055 has internal IRQs (has own IRQ domain).
29 - #interrupt-cells: Should be 1, is the local IRQ number for da9055.
Dstmpe.txt13 - interrupt-parent : Specifies which IRQ controller we're connected to
16 - irq-gpio : If present, which GPIO to use for event IRQ
Dab8500.txt5 - interrupts : contains the IRQ line for the AB8500
8 - The first cell is the AB8500 local IRQ number
18 Device IRQ Names Supply Names Description
73 - interrupts : contains the device IRQ(s) using the 2-cell format (see above)
74 - interrupt-names : contains names of IRQ resource in the order in which they were
Dpalmas.txt24 - #interrupt-cells : should be set to 2 for IRQ number and flags
25 The first cell is the IRQ number.
Dda9150.txt18 - interrupts: IRQ line info for da9150 chip.
19 - interrupt-controller: da9150 has internal IRQs (own IRQ domain).
Dtc3589x.txt18 - interrupt-parent : specifies which IRQ controller we're connected to
21 - #interrupt-cells : should be <1>, the first cell is the IRQ offset on this
32 - #interrupt-cells : should be <2>, the first cell is the IRQ offset on this
D88pm860x.txt6 - interrupts : IRQ line for the 88pm860x chip
9 - The cell is the 88pm860x local IRQ number
Darizona.txt19 - interrupts : The interrupt line the /IRQ signal for the device is
24 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
25 The first cell is the IRQ number.
Dda9062.txt20 - interrupts : IRQ line information.
24 further information on IRQ bindings.
Dqriox.txt5 It is consists of a reset controller, watchdog timer, LEDs, and 2 IRQ capable
Dhi6421.txt9 Device IRQ Names Supply Names Description
Dmax77802.txt16 - interrupts : I2C device IRQ line connected to the main SoC.
Dmax77686.txt17 - interrupts : This i2c device has an IRQ line connected to the main SoC.
Das3722.txt10 - #interrupt-cells: Should be set to 2 for IRQ number and flags.
11 The first cell is the IRQ number. IRQ numbers for different interrupt source
Dtwl-familly.txt15 - interrupts : This i2c device has an IRQ line connected to the main SoC
/linux-4.4.14/arch/mn10300/include/asm/
Dirq.h38 #define irq_canonicalize(IRQ) (IRQ) argument
/linux-4.4.14/Documentation/sound/oss/
DESS186820 For configuring the sound card's I/O addresses, IRQ and DMA, here is a
28 (INT 0 (IRQ 5 (MODE +E)))
40 the MPU-401 MIDI port is located at 0x0330. IRQ is IRQ 5, DMA is channel 1.
DPSS16 emulation. IRQ's 3,5,7,9,10,11 and 12 are available. If you
17 get IRQ errors be sure to check the interrupt is set to
28 from the IRQ used by the Microsoft Sound System port.
DCMI833085 (CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
94 (INT 0 (IRQ 7 (MODE +E)))
104 (INT 0 (IRQ 11 (MODE +E)))
121 (INT 0 (IRQ 5 (MODE +E)))
DVIBRA1635 (CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
38 (INT 0 (IRQ 5 (MODE +E)))
DIntroduction68 are available, for example IRQ, address, DMA.
299 write down what addresses, IRQ, and DMA channels
307 IRQ or DMA port that another device is using?
312 indicate what IRQ or IO port could not be obtained.
314 E) Try another port or IRQ. Note this may involve
320 sound clip repeated), you probably have either an IRQ
321 or DMA conflict. Move the card to another IRQ or DMA
323 when I had an IRQ conflict.
Dultrasound10 irq IRQ of the Sound Blaster card
DAudioExcelDSP1616 the Audio Excel hardware that you want to initialize. Check the IRQ/DMA/MIRQ
26 set up I/O addresses, IRQ lines and DMA channels. Some parameters are
DREADME.OSS144 good default configuration to use. Please try to use same I/O, DMA and IRQ
159 - "Device or resource busy". Probably the IRQ (or DMA) channel
162 - "I/O error". Almost certainly (99%) it's an IRQ or DMA conflict.
289 software selectable IRQ and DMA settings. If the (power on default) values
338 soft configuring their I/O, IRQ, DMA and shared memory resources.
359 work now. "Proper" means that I/O, IRQ and DMA settings are the same as in
644 configure the driver use I/O, IRQ and DMA settings
657 the driver to use I/O, IRQ and DMA settings which are known to work.
693 DOS based driver initializes the hardware to use known I/O, IRQ and DMA
869 Entering the I/O, IRQ and DMA config parameters
[all …]
/linux-4.4.14/drivers/sh/intc/
DKconfig24 bool "Hardware IRQ balancing support"
27 This enables support for IRQ auto-distribution mode on SH-X3
35 bool "Expose IRQ to per-controller id mapping via debugfs"
/linux-4.4.14/Documentation/scsi/
Ddtc3x80.txt16 It is memory mapped, uses an IRQ, but no dma or io-port. There is
23 The possible IRQ's (jumper selectable) are:
24 IRQ 10, 11, 12, 15
42 if you have the card jumpered to an IRQ. Probably nobody will ever
Daha152x.txt20 IRQ interrupt level (9-12; default 11)
37 -DSETUP0="{ IOPORT, IRQ, SCSI_ID, RECONNECT, PARITY, SYNCHRONOUS, DELAY, EXT_TRANS }"
40 -DSETUP1="{ IOPORT, IRQ, SCSI_ID, RECONNECT, PARITY, SYNCHRONOUS, DELAY, EXT_TRANS }"
52 aha152x=<IOPORT>[,<IRQ>[,<SCSI-ID>[,<RECONNECT>[,<PARITY>[,<SYNCHRONOUS>[,<DELAY> [,<EXT_TRANS]]]]]…
67 aha152x=IOPORT,IRQ,SCSI_ID,RECONNECT,PARITY,SYNCHRONOUS,DELAY,EXT_TRANS
71 aha152x1=IOPORT,IRQ,SCSI_ID,RECONNECT,PARITY,SYNCHRONOUS,DELAY,EXT_TRANS
80 IRQ for first and second controller
Dg_NCR5380.txt19 IRQ : 5
59 IRQ line if overridden on the command line.)
/linux-4.4.14/Documentation/devicetree/bindings/arm/altera/
Dsocfpga-sdram-edac.txt7 - interrupts : Should contain the SDRAM ECC IRQ in the
8 appropriate format for the IRQ controller.
/linux-4.4.14/arch/arm/mach-ixp4xx/include/mach/
Dentry-macro.S19 beq 1001f @ upper IRQ?
23 b 1002f @ lower IRQ being
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-vt8500.txt7 - interrupts : <IRQ> where IRQ is the interrupt number
Di2c-designware.txt7 - interrupts : <IRQ> where IRQ is the interrupt number.
/linux-4.4.14/Documentation/networking/
DPLIP.txt67 When a parallel port used for a PLIP driver has an IRQ configured to it, the
71 However, on some machines it is hard, if not impossible, to configure an IRQ
73 On these machines, the PLIP driver can be used in IRQ-less mode, where
76 the IRQ mode, because the driver has to check the parallel port many times
78 indicate that there isn't a noticeable performance drop when using IRQ-less
79 mode as compared to IRQ mode as far as the data transfer speed is involved.
82 When the PLIP driver is used in IRQ mode, the timeout used for triggering a
85 data) is, by default, 500usec. As IRQ delivery is more or less immediate,
88 When in IRQ-less mode, the PLIP driver polls the parallel port HZ times
95 10^6/HZ usecs. If both sides of a PLIP connection are used in IRQ-less mode,
Dltpc.txt11 While the driver will attempt to autoprobe the I/O port address, IRQ
22 where the parameters (in order) are the port address, IRQ, and DMA
76 SW1 IRQ 4
77 SW2 IRQ 3
78 SW3 IRQ 9 (2 in original card documentation only applies to XT)
109 IRQ autoprobing often doesn't work on a cold boot. To get around
Darcnet-hardware.txt266 - the IRQ: on 8-bit cards, it might be 2 (9), 3, 4, 5, or 7.
276 IRQ 0 - Timer 0 (Not on bus)
277 IRQ 1 - Keyboard (Not on bus)
278 IRQ 2 - IRQ Controller 2 (Not on bus, nor does interrupt the CPU)
279 IRQ 3 - COM2
280 IRQ 4 - COM1
281 IRQ 5 - FREE (LPT2 if you have it; sometimes COM3; maybe PLIP)
282 IRQ 6 - Floppy disk controller
283 IRQ 7 - FREE (LPT1 if you don't use the polling driver; PLIP)
284 IRQ 8 - Realtime Clock Interrupt (Not on bus)
[all …]
Dcops.txt28 Use modprobe like this: /sbin/modprobe cops.o (IO #) (IRQ #)
30 IRQ = 5. As of right now I would only use IRQ 5 for the card, if autoprobing.
Ddm9000.txt27 3) The IRQ line the device's interrupt pin is connected to.
60 Note the setting of the IRQ trigger flag in bast_dm9k_resource[2].flags,
62 the flags field will be passed to request_irq() when registering the IRQ
63 handler to ensure that the IRQ is setup correctly.
Dray_cs.txt94 irq_mask integer linux standard 16 bit value 1bit/IRQ
95 lsb is IRQ 0, bit 1 is IRQ 1 etc.
96 Used to restrict choice of IRQ's to use.
Dsmc9.txt17 options, such as for forcing IRQ.
D3c509.txt41 IRQ, and transceiver settings, although this capability shouldn't generally be
47 This configures the first found 3c509 card for IRQ 10, base I/O 0x310, and
50 loaded as a module, only the IRQ may be overridden. For example,
144 use the same ISA IRQ line. The common conflict is with a sound card on IRQ10
Dscaling.txt66 == RSS IRQ Configuration
68 Each receive queue has a separate IRQ associated with it. The NIC triggers
73 an IRQ may be handled on any CPU. Because a non-negligible part of packet
75 to spread receive interrupts between CPUs. To manually adjust the IRQ
76 affinity of each interrupt see Documentation/IRQ-affinity.txt. Some systems
77 will be running irqbalance, a daemon that dynamically optimizes IRQ
149 CPU. Documentation/IRQ-affinity.txt explains how CPUs are assigned to
345 the IRQ affinity table shown by /proc/interrupts. Drivers can use
355 of CPU to queues is automatically deduced from the IRQ affinities
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.freeze67 IRQ sharing is known to cause problems in some cases. It works just
69 try to shuffle around the PCI cards to give bttv another IRQ or make
70 it share the IRQ with some other piece of hardware. IRQ sharing with
72 effects with bttv sharing the IRQ with the ACPI bridge (and
/linux-4.4.14/drivers/scsi/
Deata_pio.c609 buf->IRQ = ISAirqs[z]; in get_pio_conf_PIO()
626 …printk("IRQ:%d IRQT:%d FORCADR:%d MCH:%d RIDQ:%d\n", gc->IRQ, gc->IRQ_TR, gc->FORCADR, gc->MAX_CHA… in print_pio_config()
673 …if ((buff = get_pio_board_data(base, gc->IRQ, gc->scsi_id[3], cplen = (cpu_to_be32(gc->cplen) + 1)… in register_pio_HBA()
689 if (!reg_IRQ[gc->IRQ]) { /* Interrupt already registered ? */ in register_pio_HBA()
690 if (!request_irq(gc->IRQ, do_eata_pio_int_handler, 0, "EATA-PIO", sh)) { in register_pio_HBA()
691 reg_IRQ[gc->IRQ]++; in register_pio_HBA()
693 reg_IRQL[gc->IRQ] = 1; /* IRQ is edge triggered */ in register_pio_HBA()
695 printk("Couldn't allocate IRQ %d, Sorry.\n", gc->IRQ); in register_pio_HBA()
699 if (reg_IRQL[gc->IRQ]) { in register_pio_HBA()
703 reg_IRQ[gc->IRQ]++; in register_pio_HBA()
[all …]
/linux-4.4.14/drivers/spi/
Dspi-s3c24xx-fiq.S28 @ fiq_rirq The base of the IRQ registers to find S3C2410_SRCPND
55 @@ set IRQ controller so that next op will trigger IRQ
/linux-4.4.14/Documentation/PCI/
Dpci.txt50 Register IRQ handler (request_irq())
57 Release the IRQ (free_irq())
246 Register IRQ handler (request_irq())
262 o allocate an IRQ (if BIOS did not).
361 3.6 Register IRQ handler
367 All interrupt handlers for IRQ lines should be registered with IRQF_SHARED
368 and use the devid to map IRQs to devices (remember that all PCI IRQ lines
373 IRQ lines which run from the PCI device to the Interrupt controller.
404 2) MSI avoids DMA/IRQ race conditions. DMA to host memory is guaranteed
422 Release the IRQ (free_irq())
[all …]
/linux-4.4.14/arch/sh/cchips/
DKconfig29 int "HD64461 IRQ"
33 The default setting of the HD64461 IRQ is 36.
/linux-4.4.14/arch/arm64/boot/dts/apm/
Dapm-shadowcat.dtsi86 interrupts = <1 9 0xf04>; /* GIC Maintenence IRQ */
101 interrupts = <1 0 0xff04>, /* Secure Phys IRQ */
102 <1 13 0xff04>, /* Non-secure Phys IRQ */
103 <1 14 0xff04>, /* Virt IRQ */
104 <1 15 0xff04>; /* Hyp IRQ */
/linux-4.4.14/arch/m68k/q40/
DREADME12 It seems IRQ unmasking can't be safely done on a Q40. IRQ probing
69 Make sure to configure the parallel port as SPP and remove IRQ/DMA jumpers
88 The main interrupt register IIRQ_REG will indicate whether an IRQ was internal
116 that there is no way to find out which IRQ caused a request, [EI]IRQ_REG
117 displays current state of the various IRQ lines.
/linux-4.4.14/scripts/coccinelle/misc/
Dirqf_oneshot.cocci85 msg = "ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT"
91 msg = "ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT"
/linux-4.4.14/arch/powerpc/boot/dts/fsl/
Dp1023rdb.dts186 /* IRQ[0:3] are pulled up on board, set to active-low */
211 * IRQ[4:6] only for PCIe, set to active-high,
212 * IRQ[7] is pulled up on board, set to active-low
238 * IRQ[8:10] are pulled up on board, set to active-low
239 * IRQ[11] only for PCIe, set to active-high,
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dsmsc911x.txt16 - smsc,irq-active-high : Indicates the IRQ polarity is active-high
17 - smsc,irq-push-pull : Indicates the IRQ type is push-pull
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dwm8994.txt23 - interrupts : The interrupt line the IRQ signal for the device is
30 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
31 The first cell is the IRQ number.
Datmel-classd.txt9 Should contain the IRQ line for the ClassD.
/linux-4.4.14/Documentation/m68k/
DREADME.buddha63 level of the IRQ-line of IDE port 0.
68 level of the IRQ-line of IDE port 1.
73 level of the IRQ-line of IDE port 2.
83 a buggy firmware and pull the IRQ line up
99 IRQ-lines of the IDE-ports by reading from the three (two
202 connected to the third IDE-port. The IRQ-register $f80
203 always shows a "no IRQ here" on the Buddha, and accesses to
/linux-4.4.14/Documentation/usb/
Dohci.txt26 to overhead in IRQ processing. When interrupt transfers are queued, those
28 work on while the OS is getting around to the relevant IRQ processing.
/linux-4.4.14/Documentation/serial/
Dmoxa-smartio117 as well as IRQ before installing this driver. Please refer to hardware
123 You may need to adjust IRQ usage in BIOS to avoid from IRQ conflict
127 PCI IRQ Sharing
129 Each port within the same multiport board shares the same IRQ. Up to
131 together on one system and they can share the same IRQ.
493 Error msg: Request_irq fail, IRQ(?) may be conflict with another device.
495 Other PCI or ISA devices occupy the assigned IRQ. If you are not sure
497 free IRQ and simply change another free IRQ for Moxa board.
501 Each port within the same multiport board shares the same IRQ. Please set
502 one IRQ (IRQ doesn't equal to zero) for one Moxa board.
/linux-4.4.14/Documentation/sound/alsa/
DALSA-Configuration.txt169 irq - IRQ # for AD1848 chip
311 irq - IRQ # for WSS (7,9,10,11)
315 mpu_irq - IRQ # for MPU-401 UART (3,5,7,9), -1 = disabled (default)
334 Whatever IRQ and DMA channels you pick, be sure to reserve them for
345 irq - IRQ # for WSS (7,9,10,11)
349 mpu_irq - IRQ # for MPU-401 UART (5,7,9,10), -1 = disabled (default)
368 Whatever IRQ and DMA channels you pick, be sure to reserve them for
427 wssirq - IRQ # for CMI8330 chip (WSS)
430 sbirq - IRQ # for CMI8330 chip (SB16)
468 irq - IRQ # for CS4231 chip
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dpci-keystone.txt18 pcie_msi_intc : Interrupt controller device node for MSI IRQ chip
38 pcie_intc: Interrupt controller device node for Legacy IRQ chip
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/
Dppc440spe-adma.txt38 2 sources: DMAx CS FIFO Needs Service IRQ (on UIC0)
39 and DMA Error IRQ (on UIC1). The latter is common
/linux-4.4.14/arch/arc/boot/dts/
Daxc001.dtsi35 * to uplink only 1 IRQ to ARC core intc
81 * avoid duplicating the MB dtsi file given that IRQ from
Daxc003.dtsi34 * to uplink only 1 IRQ to ARC core intc
84 * avoid duplicating the MB dtsi file given that IRQ from
Daxc003_idu.dtsi52 * to uplink only 1 IRQ to ARC core intc
106 * avoid duplicating the MB dtsi file given that IRQ from
/linux-4.4.14/Documentation/devicetree/bindings/net/can/
Datmel-can.txt6 - interrupts: Should contain IRQ line for the CAN controller
Dmicrochip,mcp251x.txt10 - interrupts: Should contain IRQ line for the CAN controller.
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dtca8418_keypad.txt9 - interrupts: IRQ line number, should trigger on falling edge
Datmel,maxtouch.txt9 - interrupts: The sink for the touchpad's IRQ output
/linux-4.4.14/Documentation/isdn/
DREADME.act200034 IRQ is configured by software. Possible values are:
53 i = Interrupt (-1 means use next free IRQ, 0 means polled mode)
62 which means: Autoprobe for an ISA card, use next free IRQ, let the
DREADME.HiSax108 io=iobase irq=IRQ mem=membase type=card_type \
206 At the moment IRQ sharing is only possible with PCI cards. Please make sure
207 that your IRQ is free and enabled for ISA use.
212 1. Teles 16.3, Euro ISDN, I/O base 280 hex, IRQ 10
215 2. Teles 16.0, 1TR6 ISDN, I/O base d80 hex, IRQ 5, Memory d0000 hex
218 3. Fritzcard, Euro ISDN, I/O base 340 hex, IRQ 10 and ELSA PCF, Euro ISDN
225 isapnp config: (INT 0 (IRQ 10 (MODE +E)))
237 6. Teles 16.3, Euro ISDN, I/O base 280 hex, IRQ 12 and
238 Teles 16.0, 1TR6, IRQ 5, Memory d0000 hex
244 7. Teles PCMCIA, Euro ISDN, I/O base 180 hex, IRQ 15 (default values)
[all …]
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DGPIO.txt156 Getting the IRQ number associated with a PIN
159 A standard gpiolib function can map the given pin number to an IRQ
160 number to pass to the IRQ system.
164 Note, not all pins have an IRQ.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Ddma.txt15 - interrupts : interrupt specifier for DMA IRQ
25 - interrupts : interrupt specifier for DMA channel IRQ
90 - interrupts : interrupt specifier for DMA channel IRQ
148 - interrupts : interrupt specifier for DMA channel IRQ
/linux-4.4.14/Documentation/devicetree/bindings/iio/light/
Dapds9300.txt13 - interrupts : interrupt mapping for GPIO IRQ
/linux-4.4.14/Documentation/devicetree/bindings/iio/magnetometer/
Dbmc150_magn.txt13 - interrupts : interrupt mapping for GPIO IRQ
/linux-4.4.14/Documentation/devicetree/bindings/iio/imu/
Dinv_mpu6050.txt9 - interrupts : interrupt mapping for GPIO IRQ
/linux-4.4.14/kernel/irq/
DKconfig1 menu "IRQ subsystem"
81 bool "Expose hardware/virtual IRQ mapping via debugfs"
/linux-4.4.14/arch/powerpc/boot/dts/
Dmedia5200.dts135 interrupts = <0 0 3 // IRQ bank 0
136 1 1 3>; // IRQ bank 1
/linux-4.4.14/Documentation/devicetree/bindings/iio/adc/
Dnuvoton-nau7802.txt10 - interrupts: IRQ line for the ADC. If not used the driver will use
Dmax1027-adc.txt8 - interrupts: IRQ line for the ADC
Dtwl4030-madc.txt8 - interrupts: IRQ line for the MADC submodule.
/linux-4.4.14/arch/cris/include/arch-v32/arch/
Dirq.h56 #define IRQ_NAME(nr) IRQ_NAME2(IRQ##nr)
/linux-4.4.14/drivers/parport/
DKconfig35 port and IRQ to be used by this driver at module load time, take a
72 will need to know which IRQ the parallel port has. By default,
75 specify which IRQ/DMA to use.
82 find out things like base addresses, IRQ lines and DMA channels. It
/linux-4.4.14/Documentation/i2c/busses/
Di2c-pca-isa15 IRQ interrupt
Di2c-parport-light20 * irq: optional IRQ
Di2c-amd811120 Flags: medium devsel, IRQ 19
Di2c-nforce236 Flags: 66Mhz, fast devsel, IRQ 5
/linux-4.4.14/Documentation/features/time/irq-time-acct/
Darch-support.txt4 # description: arch supports precise IRQ time accounting
/linux-4.4.14/Documentation/devicetree/bindings/rng/
Dst,stm32-rng.txt11 - interrupts : The designated IRQ line for the RNG
/linux-4.4.14/drivers/irqchip/
DKconfig163 tristate "Keystone 2 IRQ controller IP"
166 Support for Texas Instruments Keystone 2 IRQ controller IP which
/linux-4.4.14/arch/arm/boot/dts/
Dste-nomadik-nhk15.dts39 pins = "GPIO76_B20"; // IRQ line
51 pins = "GPIO78_A8"; // IRQ line
Dtwl6030_omap4.dtsi11 * On most OMAP4 platforms, the twl6030 IRQ line is connected
Dtwl4030_omap3.dtsi16 * On most OMAP3 platforms, the twl4030 IRQ line is connected
Dste-hrefv60plus.dtsi128 /* NFC ENA and RESET to low, pulldown IRQ line */
197 * GPIO 67 for interrupts. Pull-up the IRQ line and drive both
Domap3-pandora-600mhz.dts60 OMAP3430_CORE2_IOPAD(0x25ea, PIN_INPUT | MUX_MODE4) /* etk_d7.gpio_21 = WIFI IRQ */
Domap3-pandora-1ghz.dts60 OMAP3630_CORE2_IOPAD(0x25ea, PIN_INPUT | MUX_MODE4) /* etk_d7.gpio_21 = WIFI IRQ */
Domap4-var-som-om44.dtsi186 /* SPI = 0, IRQ# = 7, 4 = active high level-sensitive */
197 /* SPI = 0, IRQ# = 119, 4 = active high level-sensitive */
/linux-4.4.14/Documentation/devicetree/bindings/iio/pressure/
Dbmp085.txt12 - interrupts: interrupt mapping for IRQ
/linux-4.4.14/Documentation/pcmcia/
Ddriver-changes.txt42 * New IRQ request rules (as of 2.6.35)
45 - calling request_irq/free_irq directly. Use the IRQ from *p_dev->irq.
51 being; they might receive a shared IRQ nonetheless.
110 determine which IRQ should be used. Therefore, link->irq.IRQInfo2
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dzforce_ts.txt27 irq-gpios = <&gpio5 6 0>; /* IRQ, optional */
Dtsc2005.txt6 - interrupts : IRQ specifier
/linux-4.4.14/Documentation/ide/
Dide.txt21 *** For the CMD640, linux disables "IRQ unmasking" (hdparm -u1) on any
23 *** If "prefetch" is disabled (hdparm -p8), then "IRQ unmasking" can be
71 ones), for the drives/geometries attached to those interfaces, and for the IRQ
74 Any number of interfaces may share a single IRQ if necessary, at a slight
77 or may not be harmful to your hardware.. two or more cards driving the same IRQ
154 setup; I've had one report of a system which was shipped with IRQ 15
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dsunxi-ir.txt8 - interrupts : should contain IR IRQ number;
Datmel-isi.txt7 - interrupts: should contain IRQ line for the ISI;
Dti-am437x-vpfe.txt12 - interrupts: should contain IRQ line for the VPFE;
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dste-coh901318.txt9 - interrupts: the single DMA IRQ
Dbrcm,bcm2835-dma.txt4 Only the lower 13 channels have an associated IRQ.
/linux-4.4.14/Documentation/devicetree/bindings/ata/
Dbrcm,sata-brcmstb.txt11 - interrupts : interrupt mapping for SATA IRQ
Dfsl-sata.txt11 - interrupts : <interrupt mapping for SATA IRQ>
Dexynos-sata.txt8 - interrupts : <interrupt mapping for SATA IRQ>
Dqcom-sata.txt8 - interrupts : <interrupt mapping for SATA IRQ>
Dimx-sata.txt10 - interrupts : interrupt mapping for SATA IRQ
Dsata_highbank.txt10 - interrupts : <interrupt mapping for SATA IRQ>
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dpicoxcell.txt13 - interrupts : The single IRQ line for the timer.
Datmel-at91.txt47 - interrupts: Should contain interrupt for the PIT which is the IRQ line
53 - interrupts: Should contain interrupt for the ST which is the IRQ line
/linux-4.4.14/Documentation/cdrom/
Dide-cd76 address and an IRQ number, the standard assignments being
221 b. Timeout/IRQ errors.
226 - IRQ problems may also be indicated by the message
227 `IRQ probe failed (<n>)' while booting. If <n> is zero, that
229 it was expecting one (on any feasible IRQ). If <n> is negative,
230 that means the system saw interrupts on multiple IRQ lines, when
233 - Double-check your hardware configuration to make sure that the IRQ
238 the IRQ you're using. Also check the BIOS setup for your system;
239 some have the ability to disable individual IRQ levels, and I've
240 had one report of a system which was shipped with IRQ 15 disabled
/linux-4.4.14/Documentation/networking/caif/
Dspi_porting.txt54 This function can be called from IRQ context (recommended in order
63 This function can be called from IRQ context (recommended in order
122 * (and even advised) to call the ss_cb() function in IRQ context in
134 * from IRQ context. */
/linux-4.4.14/arch/arm/kernel/
Dentry-v7m.S43 @ Invoke the IRQ handler
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dflctl-nand.txt6 - interrupts : flste IRQ number
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Drenesas,pfc-pinctrl.txt34 IRQ pins. This property is mandatory when the PFC handles GPIOs and
36 external IRQ, sorted by external IRQ number.
/linux-4.4.14/arch/frv/kernel/
Dirq.c152 #error dont know external IRQ trigger levels for this setup in init_IRQ()
/linux-4.4.14/Documentation/devicetree/bindings/mips/
Dcpu_irq.txt4 IRQs from a devicetree file and create a irq_domain for IRQ controller.
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/
Dath79-ddr-controller.txt5 by the IRQ controller to flush the FIFO before running the interrupt handler
/linux-4.4.14/Documentation/devicetree/bindings/hsi/
Dnokia-modem.txt23 - interrupts: Should be IRQ handle for modem's reset indication
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Dsti-mailbox.txt20 - interrupts : Contains the IRQ line for a Rx mailbox
/linux-4.4.14/Documentation/devicetree/bindings/watchdog/
Dmarvel.txt34 - interrupts : Contains the IRQ for watchdog expiration
/linux-4.4.14/drivers/video/fbdev/omap2/dss/
DKconfig32 bool "Collect DSS IRQ statistics"
36 Collect DSS IRQ statistics, printable via debugfs.
/linux-4.4.14/arch/cris/include/arch-v10/arch/
Dirq.h108 #define IRQ_NAME(nr) IRQ_NAME2(IRQ##nr)
/linux-4.4.14/arch/metag/
DKconfig.debug17 will also use IRQ stacks to compensate for the reduced stackspace.
/linux-4.4.14/arch/arm/include/asm/hardware/
Dentry-macro-iomd.S37 2406: ldrneb \irqnr, [\tmp, \irqstat] @ get IRQ number
/linux-4.4.14/Documentation/devicetree/bindings/net/nfc/
Dtrf7970a.txt18 "IRQ Status Read" erratum.
/linux-4.4.14/Documentation/devicetree/bindings/arm/ux500/
Dboards.txt71 interrupts = <1 13 0x304>; /* IRQ level high per-CPU */
/linux-4.4.14/Documentation/virtual/kvm/arm/
Dvgic-mapped-irqs.txt33 with the virtual IRQ number and the state of the interrupt (Pending,
39 KVM must also program an additional field in the LR, the physical IRQ
40 number, to link the virtual with the physical IRQ.
173 4. At T+100 the timer fires and a physical IRQ causes the VM to exit
/linux-4.4.14/drivers/pnp/
DKconfig11 peripherals to be configured by software, e.g. assign IRQ's or other
/linux-4.4.14/Documentation/devicetree/bindings/power/
Drt9455_charger.txt9 - interrupts: interrupt mapping for GPIO IRQ, it should be

123