From: Ahmad Byagowi <ahmadexp@gmail.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Peter Rosin <peda@lysator.liu.se>,
Jakub Kicinski <kuba@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Ahmad Byagowi <ahmadexp@gmail.com>
Subject: [PATCH v7 0/3] i2c: mux: Propagate software nodes to channel adapters
Date: Sun, 23 Aug 2026 09:34:35 -0700 [thread overview]
Message-ID: <cover.1787502619.git.ahmadexp@gmail.com> (raw)
Device Tree channel nodes are associated with the adapters created by
i2c-mux, but equivalent software-node descriptions are not. Use generic
firmware-node operations for the channel lookup so child I2C devices can be
instantiated from software-node properties.
This is the I2C prerequisite split out of the Time Card series. The first
patch fixes the existing Device Tree channel-node leak on adapter-add
failure. The second factors the Device Tree lookup into a helper without
changing behavior. The third converts that helper and the node lifetime
handling to generic firmware-node operations.
The dependent ptp_ocp board profiles will be resent to net-next after the
LED and I2C prerequisites land.
---
Changes since v6:
- Split the existing Device Tree leak fix into its own patch.
- Add a preparatory patch that only factors out the OF lookup.
- Convert the helper to generic firmware-node operations in the final
patch.
- Drop the separate private software-node pointer and use the adapter's
firmware node for cleanup.
- Save the firmware node before adapter deletion, then release it
afterwards following the i2c-atr lifetime pattern.
- Rebase onto the current I2C i2c-next branch.
Validation:
- git diff --check
- strict checkpatch
- x86-64 Clang syntax check
v6: https://lore.kernel.org/r/eb4a8ab1eedd8a01ca34c6a7e0685639d0498423.1787247467.git.ahmadexp@gmail.com/
Ahmad Byagowi (3):
i2c: mux: Fix channel node leak on adapter add failure
i2c: mux: Factor out channel node lookup
i2c: mux: Propagate software nodes to channel adapters
drivers/i2c/i2c-mux.c | 96 +++++++++++++++++++++++--------------------
1 file changed, 52 insertions(+), 44 deletions(-)
base-commit: cd5fec79af3fa04e88e5900cdfa56d5525f5740b
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-08-23 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 16:34 Ahmad Byagowi [this message]
2026-08-23 16:34 ` [PATCH v7 1/3] i2c: mux: Fix channel node leak on adapter add failure Ahmad Byagowi
2026-08-23 16:34 ` [PATCH v7 2/3] i2c: mux: Factor out channel node lookup Ahmad Byagowi
2026-08-23 16:34 ` [PATCH v7 3/3] i2c: mux: Propagate software nodes to channel adapters Ahmad Byagowi
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=cover.1787502619.git.ahmadexp@gmail.com \
--to=ahmadexp@gmail.com \
--cc=andi.shyti@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
all inboxes | Powered by JetHome®