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 v2 3/9] software node: allow referencing firmware nodes
Date: Wed, 22 Oct 2025 21:59:49 +0300 [thread overview]
Message-ID: <aPkppRTFKFxqAxKp@smile.fi.intel.com> (raw)
In-Reply-To: <20251022-reset-gpios-swnodes-v2-3-69088530291b@linaro.org>
On Wed, Oct 22, 2025 at 03:41:02PM +0200, Bartosz Golaszewski wrote:
>
> 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
Still union?
> 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.
...
> - refnode = software_node_fwnode(ref->node);
> - if (!refnode)
> - return -ENOENT;
Why is this being dropped?
> + if (ref->swnode)
> + refnode = software_node_fwnode(ref->swnode);
> + else if (ref->fwnode)
> + refnode = ref->fwnode;
> + else
> + return -EINVAL;
>
...
> -#define SOFTWARE_NODE_REFERENCE(_ref_, ...) \
> +#define __SOFTWARE_NODE_REF(_ref, _type, _node, ...) \
> (const struct software_node_ref_args) { \
> - .node = _ref_, \
> + ._node = _ref, \
> .nargs = COUNT_ARGS(__VA_ARGS__), \
> .args = { __VA_ARGS__ }, \
> }
>
> +#define SOFTWARE_NODE_REF_SWNODE(_ref, ...) \
> + __SOFTWARE_NODE_REF(_ref, SOFTWARE_NODE_REF_SWNODE, \
> + swnode, __VA_ARGS__)
> +
> +#define SOFTWARE_NODE_REF_FWNODE(_ref, ...) \
> + __SOFTWARE_NODE_REF(_ref, SOFTWARE_NODE_REF_FWNODE, \
> + fwnode, __VA_ARGS__)
I do not see a point of making these three instead of two direct ones.
But I have no strong objection either.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-10-22 18:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 13:40 [PATCH v2 0/9] reset: rework reset-gpios handling Bartosz Golaszewski
2025-10-22 13:41 ` [PATCH v2 1/9] software node: read the reference args via the fwnode API Bartosz Golaszewski
2025-10-22 13:41 ` [PATCH v2 2/9] software node: increase the reference of the swnode by its fwnode Bartosz Golaszewski
2025-10-22 13:41 ` [PATCH v2 3/9] software node: allow referencing firmware nodes Bartosz Golaszewski
2025-10-22 18:59 ` Andy Shevchenko [this message]
2025-10-24 7:06 ` Bartosz Golaszewski
2025-10-24 15:17 ` Sakari Ailus
2025-10-24 15:27 ` Bartosz Golaszewski
2025-10-22 13:41 ` [PATCH v2 4/9] gpio: swnode: don't use the swnode's name as the key for GPIO lookup Bartosz Golaszewski
2025-10-22 18:44 ` Andy Shevchenko
2025-10-24 7:17 ` Bartosz Golaszewski
2025-10-22 13:41 ` [PATCH v2 5/9] gpio: swnode: update the property definitions Bartosz Golaszewski
2025-10-22 13:41 ` [PATCH v2 6/9] reset: order includes alphabetically in reset/core.c Bartosz Golaszewski
2025-10-22 13:41 ` [PATCH v2 7/9] reset: make the provider of reset-gpios the parent of the reset device Bartosz Golaszewski
2025-10-22 14:45 ` Philipp Zabel
2025-10-22 14:52 ` Bartosz Golaszewski
2025-10-22 13:41 ` [PATCH v2 8/9] reset: gpio: convert the driver to using the auxiliary bus Bartosz Golaszewski
2025-10-22 18:38 ` Andy Shevchenko
2025-10-22 13:41 ` [PATCH v2 9/9] reset: gpio: use software nodes to setup the GPIO lookup Bartosz Golaszewski
2025-10-22 14:45 ` Philipp Zabel
2025-10-23 12:20 ` [PATCH v2 0/9] reset: rework reset-gpios handling Linus Walleij
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=aPkppRTFKFxqAxKp@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