[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250531184359.370d4629@jic23-huawei>
Date: Sat, 31 May 2025 18:43:59 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Andy Shevchenko <andy@...nel.org>
Cc: Jonathan Santos <Jonathan.Santos@...log.com>, linux-iio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-acpi@...r.kernel.org, nuno.sa@...log.com,
Michael.Hennerich@...log.com, marcelo.schmitt@...log.com, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, marcelo.schmitt1@...il.com,
linus.walleij@...aro.org, brgl@...ev.pl, lgirdwood@...il.com,
broonie@...nel.org, jonath4nns@...il.com, dlechner@...libre.com,
rafael@...nel.org, djrscally@...il.com
Subject: Re: [PATCH v9 01/12] device property: add
fwnode_find_reference_args()
On Fri, 30 May 2025 20:48:14 +0300
Andy Shevchenko <andy@...nel.org> wrote:
> On Thu, May 29, 2025 at 07:48:17PM -0300, Jonathan Santos wrote:
> > Similarly to fwnode_find_reference(), find and return a named reference
> > to a fwnode handle, including its arguments. This wrapper facilitates
> > cleanup handling and improves readability.
>
> In principle I'm okay with the code, but I probably missed how this new API is
> being used (in terms of a need of those arguments to be retrieved).
>
Good point - this needs a little more justification, particularly with respect
to why we are using it in this driver.
J
Powered by blists - more mailing lists