From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 3/9] software node: allow referencing firmware nodes
Date: Mon, 13 Oct 2025 23:11:50 +0300 [thread overview]
Message-ID: <aO1dBgPZfDJTsPfE@smile.fi.intel.com> (raw)
In-Reply-To: <20251006-reset-gpios-swnodes-v1-3-6d3325b9af42@linaro.org>
On Mon, Oct 06, 2025 at 03:00:18PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> At the moment software nodes can only reference other software nodes.
> This is a limitation for devices created, for instance, on the auxiliary
> bus with a dynamic software node attached which cannot reference devices
> the firmware node of which is "real" (as an OF node or otherwise).
>
> Make it possible for a software node to reference all firmware nodes in
> addition to static software nodes. To that end: use a union of different
> pointers in struct software_node_ref_args and add an enum indicating
> what kind of reference given instance of it is. Rework the helper macros
> and deprecate the existing ones whose names don't indicate the reference
> type.
>
> Software node graphs remain the same, as in: the remote endpoints still
> have to be software nodes.
...
> +enum software_node_ref_type {
> + /* References a software node. */
> + SOFTWARE_NODE_REF_SWNODE = 0,
I don't see why we need an explicit value here.
> + /* References a firmware node. */
> + SOFTWARE_NODE_REF_FWNODE,
> +};
...
> /**
> * struct software_node_ref_args - Reference property with additional arguments
> - * @node: Reference to a software node
> + * @swnode: Reference to a software node
> + * @fwnode: Alternative reference to a firmware node handle
> * @nargs: Number of elements in @args array
> * @args: Integer arguments
> */
> struct software_node_ref_args {
> - const struct software_node *node;
> + enum software_node_ref_type type;
> + union {
> + const struct software_node *swnode;
> + struct fwnode_handle *fwnode;
> + };
Can't we always have an fwnode reference?
> unsigned int nargs;
> u64 args[NR_FWNODE_REFERENCE_ARGS];
> };
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-10-18 17:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 13:00 [PATCH 0/9] reset: rework reset-gpios handling Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 1/9] software node: read the reference args via the fwnode API Bartosz Golaszewski
2025-10-13 20:05 ` Andy Shevchenko
2025-10-22 7:51 ` Bartosz Golaszewski
2025-10-22 8:24 ` Sakari Ailus
2025-10-22 8:35 ` Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 2/9] software node: increase the reference of the swnode by its fwnode Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 3/9] software node: allow referencing firmware nodes Bartosz Golaszewski
2025-10-13 20:11 ` Andy Shevchenko [this message]
2025-10-20 8:06 ` Bartosz Golaszewski
2025-10-20 10:05 ` Andy Shevchenko
2025-10-20 11:26 ` Bartosz Golaszewski
2025-10-21 6:54 ` Sakari Ailus
2025-10-21 9:06 ` Bartosz Golaszewski
2025-10-21 9:14 ` Andy Shevchenko
2025-10-06 13:00 ` [PATCH 4/9] gpio: swnode: don't use the swnode's name as the key for GPIO lookup Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 5/9] gpio: swnode: update the property definitions Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 6/9] reset: order includes alphabetically in reset/core.c Bartosz Golaszewski
2025-10-06 15:20 ` Philipp Zabel
2025-10-06 13:00 ` [PATCH 7/9] reset: make the provider of reset-gpios the parent of the reset device Bartosz Golaszewski
2025-10-06 15:19 ` Philipp Zabel
2025-10-20 15:25 ` Bartosz Golaszewski
2025-10-21 9:17 ` Philipp Zabel
2025-10-21 9:27 ` Bartosz Golaszewski
2025-10-21 9:31 ` Philipp Zabel
2025-10-21 9:39 ` Bartosz Golaszewski
2025-10-21 14:55 ` Andy Shevchenko
2025-10-21 15:03 ` Andy Shevchenko
2025-10-21 15:23 ` Bartosz Golaszewski
2025-10-21 15:47 ` Andy Shevchenko
2025-10-22 8:39 ` Philipp Zabel
2025-10-22 12:17 ` Bartosz Golaszewski
2025-10-22 16:11 ` Andy Shevchenko
2025-10-20 15:56 ` Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 8/9] reset: gpio: convert the driver to using the auxiliary bus Bartosz Golaszewski
2025-10-06 15:22 ` Philipp Zabel
2025-10-06 13:00 ` [PATCH 9/9] reset: gpio: use software nodes to setup the GPIO lookup Bartosz Golaszewski
2025-10-06 15:55 ` Philipp Zabel
2025-10-10 14:07 ` Bartosz Golaszewski
2025-10-17 7:12 ` [PATCH 0/9] reset: rework reset-gpios handling Bartosz Golaszewski
-- strict thread matches above, loose matches on Subject: below --
2025-10-18 19:28 [PATCH 3/9] software node: allow referencing firmware nodes 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=aO1dBgPZfDJTsPfE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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