From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Ahmad Byagowi <ahmadexp@gmail.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Peter Rosin <peda@lysator.liu.se>,
Andy Shevchenko <andy@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 2/2] i2c: mux: Propagate firmware nodes to channel adapters
Date: Tue, 1 Sep 2026 11:54:04 +0300 [thread overview]
Message-ID: <apaSrJFAp5Fr6ZT1@ashevche-desk.local> (raw)
In-Reply-To: <7a4cf4b288afaaa085e1c4ec592fbb0fb43eefd4.1788181174.git.ahmadexp@gmail.com>
On Mon, Aug 31, 2026 at 10:22:07AM -0700, Ahmad Byagowi wrote:
> Device Tree channel nodes are associated with the adapters created by
> i2c-mux, but equivalent firmware-node descriptions are not.
>
> Use generic firmware-node operations for the existing channel lookup
> and associate the returned node with the adapter. Do not restrict the
> lookup by firmware-node type, so Device Tree, software nodes, and ACPI
> descriptions all follow the same property traversal. The existing
> acpi_preset_companion() call remains in place for the standard ACPI
> channel association.
>
> Keep a separate reference to the node returned by the generic lookup
> because acpi_preset_companion() may replace the device's primary
> firmware node. Release the saved reference after adapter deletion.
...
> if (muxc->arbitrator)
> - mux_node = of_get_child_by_name(dev_node, "i2c-arb");
> + mux_node = fwnode_get_named_child_node(dev_node, "i2c-arb");
> else if (muxc->gate)
> - mux_node = of_get_child_by_name(dev_node, "i2c-gate");
> + mux_node = fwnode_get_named_child_node(dev_node, "i2c-gate");
> else
> - mux_node = of_get_child_by_name(dev_node, "i2c-mux");
> + mux_node = fwnode_get_named_child_node(dev_node, "i2c-mux");
>
> if (mux_node) {
> - /* A "reg" property indicates an old-style DT entry */
> - if (!of_property_read_u32(mux_node, "reg", ®)) {
> - of_node_put(mux_node);
> + /* A "reg" property indicates an old-style firmware entry. */
> + if (!fwnode_property_read_u32(mux_node, "reg", ®)) {
> + fwnode_handle_put(mux_node);
Consider using __free(fwnode_handle) at some point. Perhaps as a patch
on top of this.
It also may help with the rest of the existing code elsewhere in the file.
> mux_node = NULL;
> }
> }
>
> if (!mux_node)
> - mux_node = of_node_get(dev_node);
> + mux_node = fwnode_handle_get(dev_node);
> else if (muxc->arbitrator || muxc->gate)
> return mux_node;
>
> - for_each_child_of_node(mux_node, child) {
> - ret = of_property_read_u32(child, "reg", ®);
> + fwnode_for_each_child_node(mux_node, child) {
> + ret = fwnode_property_read_u32(child, "reg", ®);
> if (ret)
> continue;
> if (chan_id == reg)
> break;
> }
>
> - of_node_put(mux_node);
> + fwnode_handle_put(mux_node);
> return child;
> }
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-09-01 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 17:22 [PATCH v8 0/2] i2c: mux: Propagate firmware nodes to channel adapters Ahmad Byagowi
2026-08-31 17:22 ` [PATCH v8 1/2] i2c: mux: Factor out channel node lookup Ahmad Byagowi
2026-09-01 8:50 ` Andy Shevchenko
2026-08-31 17:22 ` [PATCH v8 2/2] i2c: mux: Propagate firmware nodes to channel adapters Ahmad Byagowi
2026-09-01 8:54 ` Andy Shevchenko [this message]
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=apaSrJFAp5Fr6ZT1@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=ahmadexp@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=andy@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@lysator.liu.se \
/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