linux-kernel - Re: [PATCH v4 2/3] docs: firmware-guide: ACPI: Add named interrupt doc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJZ5v0gt+aDr_Te_mco_0CyRJAWgyeDKUb+dksfZz0mj91G0hw@mail.gmail.com>
Date:   Tue, 25 Jan 2022 18:54:46 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Akhil R <akhilrajeev@...dia.com>
Cc:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Christian König <christian.koenig@....com>,
        Dmitry Osipenko <digetx@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jon Hunter <jonathanh@...dia.com>,
        Laxman Dewangan <ldewangan@...dia.com>,
        Len Brown <lenb@...nel.org>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        linux-i2c <linux-i2c@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-tegra <linux-tegra@...r.kernel.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Sumit Semwal <sumit.semwal@...aro.org>,
        Thierry Reding <thierry.reding@...il.com>,
        Wolfram Sang <wsa@...nel.org>
Subject: Re: [PATCH v4 2/3] docs: firmware-guide: ACPI: Add named interrupt doc

On Sat, Jan 22, 2022 at 12:33 PM Akhil R <akhilrajeev@...dia.com> wrote:
>
> Add a detailed example of the named interrupts in the ACPI table.
>
> Signed-off-by: Akhil R <akhilrajeev@...dia.com>

Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>

> ---
>  Documentation/firmware-guide/acpi/enumeration.rst | 39 +++++++++++++++++++++++
>  1 file changed, 39 insertions(+)
>
> diff --git a/Documentation/firmware-guide/acpi/enumeration.rst b/Documentation/firmware-guide/acpi/enumeration.rst
> index 74b830b2..d002256 100644
> --- a/Documentation/firmware-guide/acpi/enumeration.rst
> +++ b/Documentation/firmware-guide/acpi/enumeration.rst
> @@ -143,6 +143,45 @@ In robust cases the client unfortunately needs to call
>  acpi_dma_request_slave_chan_by_index() directly and therefore choose the
>  specific FixedDMA resource by its index.
>
> +Named Interrupts
> +================
> +
> +Drivers enumerated via ACPI can have names to interrupts in the ACPI table
> +which can be used to get the IRQ number in the driver.
> +
> +The interrupt name can be listed in _DSD as 'interrupt-names'. The names
> +should be listed as an array of strings which will map to the Interrupt()
> +resource in the ACPI table corresponding to its index.
> +
> +The table below shows an example of its usage::
> +
> +    Device (DEV0) {
> +        ...
> +        Name (_CRS, ResourceTemplate() {
> +            ...
> +            Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive) {
> +                0x20,
> +                0x24
> +            }
> +        })
> +
> +        Name (_DSD, Package () {
> +            ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
> +            Package () {
> +                Package () {"interrupt-names",
> +                Package (2) {"default", "alert"}},
> +            }
> +        ...
> +        })
> +    }
> +
> +The interrupt name 'default' will correspond to 0x20 in Interrupt()
> +resource and 'alert' to 0x24. Note that only the Interrupt() resource
> +is mapped and not GpioInt() or similar.
> +
> +The driver can call the function - fwnode_irq_get_byname() with the fwnode
> +and interrupt name as arguments to get the corresponding IRQ number.
> +
>  SPI serial bus support
>  ======================
>
> --
> 2.7.4
>