4 Contact: Craig Gallek <kraig@google.com>
5 Description: Directory containing information about the system's IRQs.
6 Specifically, data from the associated struct irq_desc.
7 The information here is similar to that in /proc/interrupts
8 but in a more machine-friendly format. This directory contains
9 one subdirectory for each Linux IRQ number.
11 What: /sys/kernel/irq/<irq>/actions
14 Contact: Craig Gallek <kraig@google.com>
15 Description: The IRQ action chain. A comma-separated list of zero or more
16 device names associated with this interrupt.
18 What: /sys/kernel/irq/<irq>/chip_name
21 Contact: Craig Gallek <kraig@google.com>
22 Description: Human-readable chip name supplied by the associated device
25 What: /sys/kernel/irq/<irq>/hwirq
28 Contact: Craig Gallek <kraig@google.com>
29 Description: When interrupt translation domains are used, this file contains
30 the underlying hardware IRQ number used for this Linux IRQ.
32 What: /sys/kernel/irq/<irq>/name
35 Contact: Craig Gallek <kraig@google.com>
36 Description: Human-readable flow handler name as defined by the irq chip
39 What: /sys/kernel/irq/<irq>/per_cpu_count
42 Contact: Craig Gallek <kraig@google.com>
43 Description: The number of times the interrupt has fired since boot. This
44 is a comma-separated list of counters; one per CPU in CPU id
45 order. NOTE: This file consistently shows counters for all
46 CPU ids. This differs from the behavior of /proc/interrupts
47 which only shows counters for online CPUs.
49 What: /sys/kernel/irq/<irq>/type
52 Contact: Craig Gallek <kraig@google.com>
53 Description: The type of the interrupt. Either the string 'level' or 'edge'.
55 What: /sys/kernel/irq/<irq>/wakeup
58 Contact: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
59 Description: The wakeup state of the interrupt. Either the string
60 'enabled' or 'disabled'.