<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in sysfs-kernel-irq</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>d61e2944 - genirq: Add wakeup sysfs node to show IRQ wakeup state</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-kernel-irq#d61e2944</link>
        <description>genirq: Add wakeup sysfs node to show IRQ wakeup stateSurprisingly there is no simple way to see if the IRQ line in questionis wakeup source or not.Note that wakeup might be an OOB (out-of-band) source like GPIO linewhich makes things slightly more complicated.Add a sysfs node to cover this case.Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Tested-by: Tony Lindgren &lt;tony@atomide.com&gt;Cc: Grygorii Strashko &lt;grygorii.strashko@ti.com&gt;Cc: &quot;Rafael J . Wysocki&quot; &lt;rafael.j.wysocki@intel.com&gt;Link: https://lkml.kernel.org/r/20180226155043.67937-1-andriy.shevchenko@linux.intel.com

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-kernel-irq</description>
        <pubDate>Mon, 26 Feb 2018 15:50:43 +0000</pubDate>
        <dc:creator>Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>ecb3f394 - genirq: Expose interrupt information through sysfs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-kernel-irq#ecb3f394</link>
        <description>genirq: Expose interrupt information through sysfsInformation about interrupts is exposed via /proc/interrupts, but theformat of that file has changed over kernel versions and differs acrossarchitectures. It also has varying column numbers depending on hardware.That all makes it hard for tools to parse.To solve this, expose the information through sysfs so each irq attributeis in a separate file in a consistent, machine parsable way.This feature is only available when both CONFIG_SPARSE_IRQ andCONFIG_SYSFS are enabled.Examples:  /sys/kernel/irq/18/actions:	i801_smbus,ehci_hcd:usb1,uhci_hcd:usb7  /sys/kernel/irq/18/chip_name:	IR-IO-APIC  /sys/kernel/irq/18/hwirq:		18  /sys/kernel/irq/18/name:		fasteoi  /sys/kernel/irq/18/per_cpu_count:	0,0  /sys/kernel/irq/18/type:		level  /sys/kernel/irq/25/actions:	ahci0  /sys/kernel/irq/25/chip_name:	IR-PCI-MSI  /sys/kernel/irq/25/hwirq:		512000  /sys/kernel/irq/25/name:		edge  /sys/kernel/irq/25/per_cpu_count:	29036,0  /sys/kernel/irq/25/type:		edge[ tglx: Moved kobject_del() under sparse_irq_lock, massaged code comments  	and changelog ]Signed-off-by: Craig Gallek &lt;kraig@google.com&gt;Cc: David Decotigny &lt;decot@google.com&gt;Link: http://lkml.kernel.org/r/1473783291-122873-1-git-send-email-kraigatgoog@gmail.comSigned-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-kernel-irq</description>
        <pubDate>Tue, 13 Sep 2016 16:14:51 +0000</pubDate>
        <dc:creator>Craig Gallek &lt;kraig@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
