[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z_Txb26PyxBPM5oU@smile.fi.intel.com>
Date: Tue, 8 Apr 2025 12:50:39 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Zijun Hu <zijun_hu@...oud.com>
Cc: Zijun Hu <quic_zijuhu@...cinc.com>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>, Daniel Scally <djrscally@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Danilo Krummrich <dakr@...nel.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH v2 1/1] device property: Add a note to the fwnode.h
On Fri, Apr 04, 2025 at 01:19:32PM +0300, Andy Shevchenko wrote:
> On Fri, Apr 04, 2025 at 10:59:41AM +0800, Zijun Hu wrote:
> > On 2025/4/1 00:35, Andy Shevchenko wrote:
...
> > > + * The respective API headers should
> > > + * guarantee all the required data types and definitions without including
> > > + * this header directly into the driver.
> >
> > device property(include/linux/property.h)
> > ^
> > |
> > firmware node(include/linux/fwnode.h)
> > ^ ^ ^ ^
> > | | | |
> > DT ACPI SWNODE ...
> >
> > For various firmware implementations(DT|ACPI|SWNODE...), i feel we may
> > allow them include fwnode.h by their header or source files.
>
> That's the point, yes. And that's what exactly I put under the first sentence.
> The device property providers are not the leaf drivers in this sense.
FWIW, Rafael proposed better wording which I'm going to use in v3 in the header.
Commit message would be similar, though.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists