mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Rosin <peda@lysator.liu.se>
To: Ahmad Byagowi <ahmadexp@gmail.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
	Andy Shevchenko <andy@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 0/2] i2c: mux: Propagate firmware nodes to channel adapters
Date: Thu, 10 Sep 2026 15:47:33 +0200	[thread overview]
Message-ID: <aqK09c9nrs1946HN@gryt> (raw)
In-Reply-To: <cover.1788623619.git.ahmadexp@gmail.com>

On Mon, Sep 07, 2026 at 11:26:21PM -0700, Ahmad Byagowi wrote:
> Device Tree channel nodes are associated with the adapters created by
> i2c-mux, but equivalent firmware-node descriptions are not. Convert the
> existing lookup to generic firmware-node operations so software-node and
> ACPI descriptions can use the same property traversal.
> 
> This is the remaining I2C prerequisite split out of the Time Card series.
> The channel-node leak fix from v7 was applied to i2c-next as commit
> 385c7af4e3b9 ("i2c: mux: Fix channel node leak on adapter add failure"), so
> it is no longer included here. The first patch factors the Device Tree
> lookup into a helper without changing behavior. The second converts the
> helper and node lifetime handling to generic firmware-node operations.
> 
> The existing acpi_preset_companion() call remains in place after the generic
> lookup. A separate reference to the node returned by that lookup is retained
> because ACPI companion setup may replace the adapter's primary firmware
> node. The dependent ptp_ocp board profiles will be resent to net-next after
> the LED and I2C prerequisites land.
> 
> Changes since v9:
>   - Declare dev_node, mux_node, and child on separate lines in both patches,
>     as requested by Peter Rosin and agreed by Andy Shevchenko.
> 
> The broader __free(fwnode_handle) cleanup remains a separate follow-up.
> 
> Validation:
>   - git diff --check
>   - strict checkpatch with an 80-column limit
>   - x86-64 GCC W=1 object build of drivers/i2c/i2c-mux.o
>   - mailbox replay onto the declared base with an identical resulting tree
> 
> v9: https://lore.kernel.org/r/cover.1788298883.git.ahmadexp@gmail.com/
> 
> Ahmad Byagowi (2):
>   i2c: mux: Factor out channel node lookup
>   i2c: mux: Propagate firmware nodes to channel adapters
> 
>  drivers/i2c/i2c-mux.c | 98 +++++++++++++++++++++++--------------------
>  1 file changed, 52 insertions(+), 46 deletions(-)

Thanks!

Andi, you can pick this series now, thanks.

Cheers,
Peter

      parent reply	other threads:[~2026-09-10 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  6:26 Ahmad Byagowi
2026-09-08  6:26 ` [PATCH v10 1/2] i2c: mux: Factor out channel node lookup Ahmad Byagowi
2026-09-08 10:39   ` Andy Shevchenko
2026-09-10 13:44   ` Peter Rosin
2026-09-08  6:26 ` [PATCH v10 2/2] i2c: mux: Propagate firmware nodes to channel adapters Ahmad Byagowi
2026-09-08 10:43   ` Andy Shevchenko
2026-09-08 13:12     ` Ahmad Byagowi
2026-09-10 13:44   ` Peter Rosin
2026-09-10 13:47 ` Peter Rosin [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=aqK09c9nrs1946HN@gryt \
    --to=peda@lysator.liu.se \
    --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 \
    /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

all inboxes | Powered by JetHome®