Home
last modified time | relevance | path

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

12345678910>>...23

/linux/Documentation/translations/zh_CN/core-api/irq/
A Dirq-domain.rst18 个中断控制器都能得到非重复的Linux IRQ号（数字）分配。
22 避免了重新实现与IRQ核心系统相同的回调机制。
32 提供任何对控制器本地IRQ(hwirq)号到Linux IRQ号空间的反向映射的支持。
56 Linux IRQ号。
82 映射的优点是固定时间查找IRQ号，而且irq_descs只分配给在用的IRQ。 缺点是该表
120 会分配一个Linux IRQ号，并调用.map()回调，这样驱动就可以将Linux IRQ号编入硬件中。
138 不能动态分配Linux IRQ号，应该使用传统映射。
141 个固定的偏移来计算IRQ号，反之亦然。 缺点是需要中断控制器管理IRQ分配，并且需要为每
145 映射Linux IRQ 0-15，这样现有的ISA驱动程序就能得到正确的IRQ号。
157 将用于静态IRQ分配情况。
[all …]
A Dconcepts.rst12 什么是IRQ？
15 IRQ (Interrupt ReQuest) 指来自设备的中断请求。
17 多个设备可以连接到同一个引脚，从而共享一个IRQ。
19 IRQ编号是用来描述硬件中断源的内核标识符。通常它是一个到全局irq_desc数组的索引，
22 IRQ编号是对机器上可能的中断源的枚举。通常枚举的是系统中所有中断控制器的输入引脚
25 体系结构可以给IRQ号赋予额外的含义，在涉及到硬件手动配置的情况下，我们鼓励这样做。
26 ISA IRQ是赋予这种额外含义的一个典型例子。
A Dirq-affinity.rst12 SMP IRQ 亲和性
20 /proc/irq/IRQ#/smp_affinity和/proc/irq/IRQ#/smp_affinity_list指定了哪些CPU能
21 够关联到一个给定的IRQ源，这两个文件包含了这些指定cpu的cpu位掩码(smp_affinity)和cpu列
22 表(smp_affinity_list)。它不允许关闭所有CPU， 同时如果IRQ控制器不支持中断请求亲和
23 (IRQ affinity)，那么所有cpu的默认值将保持不变(即关联到所有CPU).
25 /proc/irq/default_smp_affinity指明了适用于所有非激活IRQ的默认亲和性掩码。一旦IRQ被
50 现在让我们把这个IRQ限制在CPU(4-7)。
/linux/Documentation/translations/zh_CN/core-api/
A Dgenericirq.rst18 Linux通用IRQ处理
64 这两个IRQ类型共享许多低级的细节，但有不同的流处理。
95 2. 高级别的IRQ流处理器
146 电平触发型IRQ流处理程序
211 电平触发型IRQ流处理器
223 默认的需回应IRQ流处理器
234 默认的边沿触发型IRQ流处理器
257 默认的简单型IRQ流处理器
287 EOI边沿型IRQ流处理器
293 坏的IRQ流处理器
[all …]
/linux/Documentation/translations/zh_CN/PCI/
A Dpci.rst64 - 禁用设备产生的IRQ
284 注册IRQ处理函数
289 所有IRQ线的中断处理程序都应该用 ``IRQF_SHARED`` 注册，并使用devid将IRQ映射
341 停止设备上的IRQ
346 当共享的IRQ处理程序被“解钩”时，使用同一IRQ线的其余设备仍然需要启用该IRQ。因此，
347 如果“脱钩”的设备断言IRQ线，假设它是其余设备中的一个断言IRQ线，系统将作出反应。
348 由于其他设备都不会处理这个IRQ，系统将“挂起”，直到它决定这个IRQ不会被处理并屏蔽
349 这个IRQ（100,000次之后）。一旦共享的IRQ被屏蔽，其余设备将停止正常工作。这不是
355 释放IRQ
358 的IRQ被处理后返回控制，从该IRQ上“解钩”驱动程序的IRQ处理程序，最后如果没有人
[all …]
/linux/Documentation/arm/
A Dinterrupts.rst16 Secondly, the IRQ subsystem.
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.
95 set the IRQ type.
104 - per-IRQ handler
113 further IRQ events should the IRQ happen again while processing. The
[all …]
/linux/Documentation/translations/zh_CN/
A Dgpio.txt61 - 输入通常可作为 IRQ 信号,一般是沿触发,但有时是电平触发。这样的 IRQ
194 休眠，这不能在 IRQ 例程(中断上下文)中执行。
358 GPIO 映射到 IRQ
360 GPIO 编号是无符号整数;IRQ 编号也是。这些构成了两个逻辑上不同的命名空间
363 /* 映射 GPIO 编号到 IRQ 编号 */
366 /* 映射 IRQ 编号到 GPIO 编号 (尽量避免使用) */
372 并非来源于gpio_to_irq()的 IRQ 编号。
377 它们通常通过板级特定的初始化代码存放到平台设备的 IRQ 资源中。注意:IRQ
382 比如在 IRQ 是沿触发时初始化或更新驱动状态。注意某些平台不支持反映射,所以
430 片上系统一般有几个这样的区块。)某些系统可以通过输出 GPIO 触发 IRQ，
[all …]
A DIRQ.txt25 何为 IRQ?
27 一个 IRQ 是来自某个设备的一个中断请求。目前，它们可以来自一个硬件引脚，
28 或来自一个数据包。多个设备可能连接到同个硬件引脚，从而共享一个 IRQ。
30 一个 IRQ 编号是用于告知硬件中断源的内核标识。通常情况下，这是一个
34 一个 IRQ 编号是设备上某个可能的中断源的枚举。通常情况下，枚举的编号是
38 架构可以对 IRQ 编号指定额外的含义，在硬件涉及任何手工配置的情况下，
39 是被提倡的。ISA 的 IRQ 是一个分配这类额外含义的典型例子。
/linux/Documentation/translations/zh_TW/
A Dgpio.txt61 - 輸入通常可作爲 IRQ 信號,一般是沿觸發,但有時是電平觸發。這樣的 IRQ
194 休眠，這不能在 IRQ 例程(中斷上下文)中執行。
358 GPIO 映射到 IRQ
360 GPIO 編號是無符號整數;IRQ 編號也是。這些構成了兩個邏輯上不同的命名空間
363 /* 映射 GPIO 編號到 IRQ 編號 */
366 /* 映射 IRQ 編號到 GPIO 編號 (儘量避免使用) */
372 並非來源於gpio_to_irq()的 IRQ 編號。
377 它們通常通過板級特定的初始化代碼存放到平台設備的 IRQ 資源中。注意:IRQ
382 比如在 IRQ 是沿觸發時初始化或更新驅動狀態。注意某些平台不支持反映射,所以
430 片上系統一般有幾個這樣的區塊。)某些系統可以通過輸出 GPIO 觸發 IRQ，
[all …]
A DIRQ.txt26 何爲 IRQ?
28 一個 IRQ 是來自某個設備的一個中斷請求。目前，它們可以來自一個硬體引腳，
29 或來自一個數據包。多個設備可能連接到同個硬體引腳，從而共享一個 IRQ。
31 一個 IRQ 編號是用於告知硬體中斷源的內核標識。通常情況下，這是一個
35 一個 IRQ 編號是設備上某個可能的中斷源的枚舉。通常情況下，枚舉的編號是
39 架構可以對 IRQ 編號指定額外的含義，在硬體涉及任何手工配置的情況下，
40 是被提倡的。ISA 的 IRQ 是一個分配這類額外含義的典型例子。
/linux/Documentation/core-api/irq/
A Dirq-domain.rst6 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
20 be chosen so they matched the hardware IRQ line into the root
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
39 be easily extended to support other IRQ topology data sources.
100 the hwirq, and the IRQ number is stored in the table.
151 Linux IRQ number into the hardware.
201 is supporting both dynamic and static IRQ assignments.
207 for the static IRQ assignment case.
[all …]
A Dconcepts.rst2 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
A Dirq-affinity.rst2 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/Documentation/devicetree/bindings/interrupt-controller/
A 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.
A 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
/linux/Documentation/misc-devices/
A Dpci-endpoint-test.rst16 #) raise legacy IRQ
17 #) raise MSI IRQ
18 #) raise MSI-X IRQ
34 Tests legacy IRQ
42 Changes driver IRQ type configuration. The IRQ type
45 Gets driver IRQ type configuration.
/linux/Documentation/ia64/
A Dirq-redir.rst2 IRQ affinity on IA64 platforms
8 By writing to /proc/irq/IRQ#/smp_affinity the interrupt routing can be
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/arch/sh/boards/mach-microdev/
A 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/Documentation/core-api/
A Dgenericirq.rst4 Linux generic IRQ handling
23 generic IRQ handling layer.
72 transparent IRQ subsystem design.
104 2. High-level IRQ flow handlers
154 High-level IRQ flow handlers
222 Default Level IRQ flow handler
235 Default Fast EOI IRQ flow handler
247 Default Edge IRQ flow handler
271 Default simple IRQ flow handler
304 EOI Edge IRQ flow handler
[all …]
/linux/drivers/pinctrl/renesas/
A Dpfc-r8a73a4.c238 #define IRQ(a) IRQ##a##_MARK macro
287 IRQ(40), enumerator
299 F1(TXP2), F1(COEX_0), F1(COEX_1), IRQ(19), IRQ(18), /* Port85 */ enumerator
303 F1(KEYIN5), F1(KEYIN6), IRQ(41), F1(KEYIN7), IRQ(42), enumerator
305 F2(KEYOUT4), F2(KEYOUT5), IRQ(43), F2(KEYOUT6), IRQ(44), /* Port110 */ enumerator
326 IRQ(20), /* Port160 */ enumerator
327 IRQ(21), IRQ(22), IRQ(23), enumerator
331 IRQ(24), IRQ(25), IRQ(26), IRQ(27), enumerator
410 IRQ(17), IRQ(28), IRQ(29), IRQ(30), IRQ(53), IRQ(54), enumerator
411 IRQ(55), IRQ(56), IRQ(57), enumerator
[all …]
/linux/Documentation/power/
A 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
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.
127 to individual interrupt handlers, so sharing an IRQ between a system wakeup
131 In rare cases an IRQ can be shared between a wakeup device driver and an
[all …]
/linux/Documentation/devicetree/bindings/rtc/
A 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/Documentation/virt/kvm/devices/
A Dmpic.rst34 IRQ input line for each standard openpic source. 0 is inactive and 1
41 "attr" is the IRQ number. IRQ numbers for standard sources are the
44 IRQ Routing:
46 The MPIC emulation supports IRQ routing. Only a single MPIC device can
58 Access to non-SRC interrupts is not implemented through IRQ routing mechanisms.
/linux/Documentation/x86/i386/
A 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/Documentation/driver-api/gpio/
A Ddriver.rst265 It is legal for any IRQ consumer to request an IRQ from any irqchip even if it
272 the IRQ is used.
333 runtime) can't be used in a chained IRQ handler.
337 this way it will become a threaded IRQ handler on -RT and a hard IRQ handler
341 so the IRQ core will complain if it is called from an IRQ handler which is
359 for each detected GPIO IRQ
402 :header: GPIO line offset, Hardware IRQ
556 Locking IRQ usage
568 to mark the GPIO as being used as an IRQ::
612 Real-Time compliance for GPIO IRQ chips
[all …]

Completed in 82 milliseconds

12345678910>>...23