Home
last modified time | relevance | path

Searched refs:IRQ (Results 1 – 25 of 541) sorted by relevance

12345678910>>...22

/Linux-v5.4/Documentation/arm/
Dinterrupts.rst16 Secondly, the IRQ subsystem.
39 SA1111 IRQ handler, SA1111 IRQs can hold off SMC9196 IRQs indefinitely.
48 We also bring the idea of an IRQ "chip" (mainly to reduce the size of
57 * Acknowledge the IRQ.
58 * If this is a level-based IRQ, then it is expected to mask the IRQ
63 * Mask the IRQ in hardware.
67 * Unmask the IRQ in hardware.
71 * Re-run the IRQ
75 * Set the type of the IRQ.
90 the hardware IRQ if possible. If not, may call the handler
[all …]
/Linux-v5.4/Documentation/translations/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-v5.4/Documentation/
DIRQ-domain.txt6 space where each separate IRQ source is assigned a different number.
10 IRQ numbers.
15 mechanisms as the IRQ core system by modelling their interrupt
19 hardware interrupt numbers: whereas in the past, IRQ numbers could
20 be chosen so they matched the hardware IRQ line into the root
25 interrupt numbers, called hardware irq's, from Linux IRQ numbers.
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
32 The irq_domain library adds mapping between hwirq and IRQ numbers on
39 be easily extended to support other IRQ topology data sources.
51 between hwirq and IRQ numbers. Mappings are added to the irq_domain
[all …]
DIRQ.txt2 What is an IRQ?
5 An IRQ is an interrupt request from a device.
8 sharing an IRQ.
10 An IRQ number is a kernel identifier used to talk about a hardware
15 An IRQ number is an enumeration of the possible interrupt sources on a
21 Architectures can assign additional meaning to the IRQ numbers, and
DIRQ-affinity.txt2 SMP IRQ affinity
10 /proc/irq/IRQ#/smp_affinity and /proc/irq/IRQ#/smp_affinity_list specify
11 which target CPUs are permitted for a given IRQ source. It's a bitmask
13 allowed to turn off all CPUs, and if an IRQ controller does not support
14 IRQ affinity then the value will not change from the default of all cpus.
17 to all non-active IRQs. Once IRQ is allocated/activated its affinity bitmask
43 Now lets restrict that IRQ to CPU(4-7).
/Linux-v5.4/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
/Linux-v5.4/Documentation/ia64/
Dirq-redir.rst2 IRQ affinity on IA64 platforms
8 By writing to /proc/irq/IRQ#/smp_affinity the interrupt routing can be
10 that described in Documentation/IRQ-affinity.txt for i386 systems.
13 IRQ target is one particular CPU and cannot be a mask of several
29 Set the default route for IRQ number 41 to CPU 6 in lowest priority
36 cat /proc/irq/IRQ#/smp_affinity
48 If the platform features IRQ redirection (info provided by SAL) all
52 for the IRQ routing. Currently in Linux XTP registers can have three
59 The IRQ is routed to the CPU with lowest XTP register value, the
77 For systems like the NEC AzusA we get IRQ node-affinity for free. This
/Linux-v5.4/Documentation/misc-devices/
Dpci-endpoint-test.txt11 *) raise legacy IRQ
12 *) raise MSI IRQ
13 *) raise MSI-X IRQ
26 PCITEST_LEGACY_IRQ: Tests legacy IRQ
31 PCITEST_SET_IRQTYPE: Changes driver IRQ type configuration. The IRQ type
33 PCITEST_GET_IRQTYPE: Gets driver IRQ type configuration.
/Linux-v5.4/arch/sh/boards/mach-microdev/
Dirq.c42 # error Inconsistancy in defining the IRQ# for Keyboard!
46 # error Inconsistancy in defining the IRQ# for Ethernet!
50 # error Inconsistancy in defining the IRQ# for USB!
54 # error Inconsistancy in defining the IRQ# for PS/2 Mouse!
58 # error Inconsistancy in defining the IRQ# for secondary IDE!
62 # error Inconsistancy in defining the IRQ# for primary IDE!
/Linux-v5.4/Documentation/devicetree/bindings/crypto/
Dfsl-imx-scc.txt6 - interrupts : Should contain interrupt numbers for SCM IRQ and SMN IRQ.
8 SCM IRQ and SMN IRQ.
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
/Linux-v5.4/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.
29 Example isl12057 node without IRQ#2 pin connected (no alarm support):
37 Example isl12057 node with IRQ#2 pin connected to main SoC via MPP6 (note
40 SoC, and the main function of the MPP used as IRQ line, i.e.
67 Example isl12057 node without IRQ#2 pin connected to the SoC but to a
/Linux-v5.4/Documentation/power/
Dsuspend-and-interrupts.rst43 The IRQF_NO_SUSPEND flag is used to indicate that to the IRQ subsystem when
45 leave the corresponding IRQ enabled so as to allow the interrupt to work as
50 Note that the IRQF_NO_SUSPEND flag affects the entire IRQ and not just one
51 user of it. Thus, if the IRQ is shared, all of the interrupt handlers installed
54 the IRQ's users. For this reason, using IRQF_NO_SUSPEND and IRQF_SHARED at the
75 The IRQ subsystem provides two helper functions to be used by device drivers for
77 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
80 Calling enable_irq_wake() causes suspend_device_irqs() to treat the given IRQ
81 in a special way. Namely, the IRQ remains enabled, by on the first interrupt
105 IRQ subsystem to trigger a system wakeup.
[all …]
/Linux-v5.4/drivers/pinctrl/sh-pfc/
Dpfc-r8a73a4.c238 #define IRQ(a) IRQ##a##_MARK macro
240 F1(LCDD0), F3(PDM2_CLK_0), F7(DU0_DR0), IRQ(0), /* Port0 */ enumerator
241 F1(LCDD1), F3(PDM2_DATA_1), F7(DU0_DR19), IRQ(1), enumerator
242 F1(LCDD2), F3(PDM3_CLK_2), F7(DU0_DR2), IRQ(2), enumerator
243 F1(LCDD3), F3(PDM3_DATA_3), F7(DU0_DR3), IRQ(3), enumerator
244 F1(LCDD4), F3(PDM4_CLK_4), F7(DU0_DR4), IRQ(4), enumerator
245 F1(LCDD5), F3(PDM4_DATA_5), F7(DU0_DR5), IRQ(5), enumerator
246 F1(LCDD6), F3(PDM0_OUTCLK_6), F7(DU0_DR6), IRQ(6), enumerator
247 F1(LCDD7), F3(PDM0_OUTDATA_7), F7(DU0_DR7), IRQ(7), enumerator
248 F1(LCDD8), F3(PDM1_OUTCLK_8), F7(DU0_DG0), IRQ(8), enumerator
[all …]
/Linux-v5.4/Documentation/virt/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-v5.4/Documentation/core-api/
Dgenericirq.rst4 Linux generic IRQ handling
23 generic IRQ handling layer.
51 This split implementation of high-level IRQ handlers allows us to
56 The original general IRQ implementation used hw_interrupt_type
61 ``ioapic_edge_irq`` IRQ-type which share many of the low-level details but
67 Analysing a couple of architecture's IRQ subsystem implementations
71 IRQ flow itself but not in the chip details - and thus provides a more
72 transparent IRQ subsystem design.
82 IRQ-flow implementation for 'level type' interrupts and add a
89 enables smaller and cleaner IRQ subsystems. It's deprecated for three
[all …]
/Linux-v5.4/Documentation/driver-api/gpio/
Ddriver.rst63 - method to return the IRQ number associated to a given GPIO line
87 atomic context on realtime kernels (inside hard IRQ handlers and similar
261 The IRQ portions of the GPIO block are implemented using an irq_chip, using
265 It is legal for any IRQ consumer to request an IRQ from any irqchip even if it
266 is a combined GPIO+IRQ driver. The basic premise is that gpio_chip and
270 gpiod_to_irq() is just a convenience function to figure out the IRQ for a
272 the IRQ is used.
315 an SoC. This means that there is a fast IRQ flow handler for the GPIOs that
316 gets called in a chain from the parent IRQ handler, most typically the
331 Realtime considerations: Note that chained IRQ handlers will not be forced
[all …]
/Linux-v5.4/Documentation/x86/i386/
DIO-APIC.rst17 distribute IRQ load further.
40 none of those IRQ sources is performance-critical.
44 you can use the pirq= boot parameter to 'hand-construct' IRQ entries. This
52 connected to the PCI chipset IRQ routing facility (the incoming PIRQ1-4
65 Every PCI card emits a PCI IRQ, which can be INTA, INTB, INTC or INTD::
79 a card in slot4, issuing INTA IRQ, it will end up as a signal on PIRQ4 of
81 between the PIRQ lines. (distributing IRQ sources properly is not a
103 [value '0' is a generic 'placeholder', reserved for empty (or non-IRQ emitting)
107 permute all IRQ numbers properly ... it will take some time though. An
/Linux-v5.4/Documentation/scsi/
Dg_NCR5380.txt16 for the correct IRQ line automatically. If the irq parameter is 0 or 255
17 then no IRQ will be used.
53 E.g. a port mapped NCR5380 board, driver to probe for IRQ:
58 E.g. a memory mapped NCR53C400 board with no IRQ:
63 E.g. two cards, DTC3181 (in non-PnP mode) at 0x240 with no IRQ
64 and HP C2502 at 0x300 with IRQ 7:
/Linux-v5.4/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
/Linux-v5.4/arch/arc/kernel/
Dentry-compact.S118 ;##################### Scratch Mem for IRQ stack switching #############
152 ; if L2 IRQ interrupted a L1 ISR, disable preemption
155 ; -L1 IRQ taken
157 ; -preemption off IRQ, user task in syscall picked to run
170 bbit0 r9, STATUS_A1_BIT, 1f ; L1 not active when L2 IRQ, so normal
321 ; Restore the saved sys context (common exit-path for EXCPN/IRQ/Trap)
322 ; IRQ shd definitely not happen between now and rtie
335 ; use the same priority as rtie: EXCPN, L2 IRQ, L1 IRQ, None
358 ; if L2 IRQ interrupted an L1 ISR, we'd disabled preemption earlier
365 bbit0 r9, STATUS_A1_BIT, 149f ; L1 not active when L2 IRQ, so normal
/Linux-v5.4/Documentation/PCI/endpoint/
Dpci-test-function.rst44 Bit 0 raise legacy IRQ
45 Bit 1 raise MSI IRQ
46 Bit 2 raise MSI-X IRQ
65 Bit 6 IRQ raised
83 for the READ/WRITE/COPY and raise IRQ (Legacy/MSI) commands.

12345678910>>...22