From: Wolfram Sang <wsa@kernel.org>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: u.kleine-koenig@pengutronix.de, andy.shevchenko@gmail.com,
christian.koenig@amd.com, digetx@gmail.com,
gregkh@linuxfoundation.org, jonathanh@nvidia.com,
ldewangan@nvidia.com, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
rafael@kernel.org, sumit.semwal@linaro.org,
thierry.reding@gmail.com
Subject: Re: [PATCH v5 1/3] device property: Add fwnode_irq_get_byname
Date: Fri, 28 Jan 2022 22:43:08 +0100 [thread overview]
Message-ID: <YfRjbOM7kAab+o2a@shikoro> (raw)
In-Reply-To: <1643370267-31804-2-git-send-email-akhilrajeev@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
On Fri, Jan 28, 2022 at 05:14:25PM +0530, Akhil R wrote:
> Add fwnode_irq_get_byname() to get an interrupt by name from either
> ACPI table or Device Tree, whichever is used for enumeration.
>
> In the ACPI case, this allow us to use 'interrupt-names' in
> _DSD which can be mapped to Interrupt() resource by index.
> The implementation is similar to 'interrupt-names' in the
> Device Tree.
>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-28 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 11:44 [PATCH v5 0/3] Enable named interrupt smbus-alert for ACPI Akhil R
2022-01-28 11:44 ` [PATCH v5 1/3] device property: Add fwnode_irq_get_byname Akhil R
2022-01-28 21:43 ` Wolfram Sang [this message]
2022-01-28 11:44 ` [PATCH v5 2/3] docs: firmware-guide: ACPI: Add named interrupt doc Akhil R
2022-01-28 21:43 ` Wolfram Sang
2022-01-28 11:44 ` [PATCH v5 3/3] i2c: smbus: Use device_*() functions instead of of_*() Akhil R
2022-01-28 21:43 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YfRjbOM7kAab+o2a@shikoro \
--to=wsa@kernel.org \
--cc=akhilrajeev@nvidia.com \
--cc=andy.shevchenko@gmail.com \
--cc=christian.koenig@amd.com \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).