From: "Jean-François Lessard" <jefflessard3@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] device property: Add scoped fwnode child node iterators
Date: Fri, 29 Aug 2025 07:34:17 -0400 [thread overview]
Message-ID: <AA99AF86-CD2A-4BBE-92BC-3D9005E7BA3B@gmail.com> (raw)
In-Reply-To: <2025082953-splendor-unsold-e4f2@gregkh>
Le 29 août 2025 00 h 23 min 22 s HAE, Greg Kroah-Hartman <gregkh@linuxfoundation.org> a écrit :
>On Thu, Aug 28, 2025 at 10:17:59PM -0400, Jean-François Lessard wrote:
>> Add scoped versions of fwnode child node iterators that automatically
>> handle reference counting cleanup using the __free() attribute:
>>
>> - fwnode_for_each_child_node_scoped()
>> - fwnode_for_each_named_child_node_scoped()
>> - fwnode_for_each_available_child_node_scoped()
>>
>> These macros follow the same pattern as existing scoped iterators in the
>> kernel, ensuring fwnode references are automatically released when the
>> iterator variable goes out of scope. This prevents resource leaks and
>> eliminates the need for manual cleanup in error paths.
>>
>> The implementation mirrors the non-scoped variants but uses
>> __free(fwnode_handle) for automatic resource management, providing a safer
>> and more convenient interface for drivers iterating over firmware node
>> children.
>>
>> Signed-off-by: Jean-François Lessard <jefflessard3@gmail.com>
>> ---
>>
>> Notes:
>> checkpatch reports false positives that are intentionally ignored:
>> COMPLEX_MACRO, MACRO_ARG_REUSE, MACRO_ARG_PRECEDENCE
>> This is a standard iterator pattern following kernel conventions.
>>
>> include/linux/property.h | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/include/linux/property.h b/include/linux/property.h
>> index 82f0cb3ab..279c244db 100644
>> --- a/include/linux/property.h
>> +++ b/include/linux/property.h
>> @@ -176,6 +176,20 @@ struct fwnode_handle *fwnode_get_next_available_child_node(
>> for (child = fwnode_get_next_available_child_node(fwnode, NULL); child;\
>> child = fwnode_get_next_available_child_node(fwnode, child))
>>
>> +#define fwnode_for_each_child_node_scoped(fwnode, child) \
>> + for (struct fwnode_handle *child __free(fwnode_handle) = \
>> + fwnode_get_next_child_node(fwnode, NULL); \
>> + child; child = fwnode_get_next_child_node(fwnode, child))
>> +
>> +#define fwnode_for_each_named_child_node_scoped(fwnode, child, name) \
>> + fwnode_for_each_child_node_scoped(fwnode, child) \
>> + for_each_if(fwnode_name_eq(child, name))
>> +
>> +#define fwnode_for_each_available_child_node_scoped(fwnode, child) \
>> + for (struct fwnode_handle *child __free(fwnode_handle) = \
>> + fwnode_get_next_available_child_node(fwnode, NULL); \
>> + child; child = fwnode_get_next_available_child_node(fwnode, child))
>> +
>> struct fwnode_handle *device_get_next_child_node(const struct device *dev,
>> struct fwnode_handle *child);
>>
>
>We need a real user of this before we can add them, so please do that as
>part of a patch series.
>
I understand the "no dead code" policy, but I found existing manual
implementations of this exact pattern in the current kernel.
For example, drivers/i2c/i2c-core-slave.c already does:
struct fwnode_handle *child __free(fwnode_handle) = NULL;
...
fwnode_for_each_child_node(fwnode, child) {
...
}
This suggests developers are already wanting this functionality but
implementing it manually.
If included with my driver series, I would only add the
fwnode_for_each_available_child_node_scoped() variant that I actually use,
avoiding any dead code.
Best Regards
Jean-François Lessard
next prev parent reply other threads:[~2025-08-29 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 2:17 [PATCH] device property: Add scoped fwnode child node iterators Jean-François Lessard
2025-08-29 4:23 ` Greg Kroah-Hartman
2025-08-29 11:34 ` Jean-François Lessard [this message]
2025-08-29 11:39 ` Greg Kroah-Hartman
2025-09-01 6:11 ` Andy Shevchenko
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=AA99AF86-CD2A-4BBE-92BC-3D9005E7BA3B@gmail.com \
--to=jefflessard3@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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).