[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM5PR12MB185082C3D5047815F18F42BCC05B9@DM5PR12MB1850.namprd12.prod.outlook.com>
Date: Fri, 21 Jan 2022 12:29:44 +0000
From: Akhil R <akhilrajeev@...dia.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
CC: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Christian Koenig <christian.koenig@....com>,
Dmitry Osipenko <digetx@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jonathan 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 v3 1/3] device property: Add device_irq_get_byname
> Thanks, my comments below.
>
> > Add device_irq_get_byname() to get an interrupt by name from both the
> > ACPI table and the Device Tree.
>
> This needs to be clarified (it's not and, but or), what about:
>
> Add device_irq_get_byname() to get an interrupt by name from either
> ACPI table or Device Tree whichever has it.
Does 'whichever has it' mean a bit different here? Would it be good like this -?
Add fwnode_irq_get_byname() to get an interrupt by name from either
ACPI table or Device Tree, whichever is used for enumeration.
Okay with the other comments.
Thanks,
Akhil
Powered by blists - more mailing lists