[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_9Mx0AoMDlrbpPV@smile.fi.intel.com>
Date: Wed, 16 Apr 2025 09:23:03 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
Jai Luthra <jai.luthra@...asonboard.com>, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: [PATCH v4 3/7] i2c: core: Switch to fwnode APIs to get IRQ
On Tue, Apr 15, 2025 at 10:06:06PM +0200, Wolfram Sang wrote:
> On Mon, Apr 14, 2025 at 01:01:53PM +0300, Andy Shevchenko wrote:
> > Switch to fwnode APIs to get IRQ. In particular this enables
> > a support of the separate wakeup IRQ. The rest is converted
>
> You mean it enables the support of wakeup irqs for ACPI? Otherwise I
> wouldn't know what you mean here...
Re-reading this I'm also puzzled if I was interrupted in the middle
of writing it :-) From the code perspective, yes, I meant something
like that (rather "in non-OF cases").
> > just for the sake of consistency and fwnode reuse.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists