From: Herve Codina <herve.codina@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Andi Shyti <andi.shyti@kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Peter Rosin <peda@lysator.liu.se>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Allan Nielsen <allan.nielsen@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>,
Steen Hegelund <steen.hegelund@microchip.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>
Subject: [PATCH v9 0/3] lan966x pci device: Add support for SFPs, i2c part
Date: Wed, 4 Nov 2026 14:53:03 +0100 [thread overview]
Message-ID: <20261104135324.492692-1-herve.codina@bootlin.com> (raw)
Hi,
Previously, I sent a big picture series adding support for SFP ports
available on the LAN966x PCI device [0].
In this series patches touch several parts and sub-system in the kernel.
Reviews have be done and it makes sense to split the series and send
parts separately.
This current series is the extraction of patches related to issues in
the I2C subsystem. It has to be seen as a continuation of the big
picture series but related to this specific I2C part.
Those patches are related fw_delink issues specific to I2C muxes and
atrs.
They purpose is to correctly set a link between an adapter supplier and
its consumer. Indeed, an i2c mux/atr adapter's parent is not the i2c
mux/atr supplier but the adapter the i2c mux/atr is connected to. Adding
a new link between the adapter supplier involved when i2c muxes/atrs are
used avoid a freeze observed during device removal.
[0] https://lore.kernel.org/all/20260325143555.451852-1-herve.codina@bootlin.com/
Compared to the previous iteration, this v9 iteration updates i2c-atr.c
with the same modification done in i2c-mux.c. Indeed, atr and mux are
pretty similar and the exact same modifications for the exact same
reason can be done in both files (reported in v8 by Peter Rosin).
If having both atr and mux modifications in one commits is not
acceptable, let me know and I will split them in different commits.
Worth noting that I tested modifications done in mux but not in atr.
Indeed, I don't have any atr devices on the different board I have to
perform a test.
Best regards,
Hervé
Changes:
v8 -> v9
v8: https://lore.kernel.org/all/20260630103010.413688-1-herve.codina@bootlin.com/
Rebase on top of v7.4-rc1
Patches 2 and 3
- Add same modifications in i2c-atr.c than the ones done in i2c-mux.c.
- Update commit logs accordingly.
v7 -> v8
v7: https://lore.kernel.org/all/20260605083158.28ac874f@bootlin.com/
Rebase on top of v7.2-rc1
No other changes
v6 -> v7
Rebase on top of v7.1-rc1
- Patch 1, 2 and 3
No changes
Older iterations:
Patches 14, 15 and 16in the big picture series
https://lore.kernel.org/all/20260325143555.451852-1-herve.codina@bootlin.com/
Herve Codina (3):
i2c: core: Introduce i2c_get_adapter_physdev()
i2c: {mux,atr}: Set adapter physical device
i2c: {mux,atr}: Create missing devlink between mux/atr and adapter
physical device
drivers/i2c/i2c-atr.c | 26 ++++++++++++++++++++++++++
drivers/i2c/i2c-core-base.c | 16 ++++++++++++++++
drivers/i2c/i2c-mux.c | 26 ++++++++++++++++++++++++++
include/linux/i2c.h | 3 +++
4 files changed, 71 insertions(+)
--
2.56.0
next reply other threads:[~2026-11-04 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 13:53 Herve Codina [this message]
2026-11-04 13:53 ` [PATCH v9 1/3] i2c: core: Introduce i2c_get_adapter_physdev() Herve Codina
2026-11-04 13:53 ` [PATCH v9 2/3] i2c: {mux,atr}: Set adapter physical device Herve Codina
2026-11-04 13:53 ` [PATCH v9 3/3] i2c: {mux,atr}: Create missing devlink between mux/atr and " Herve Codina
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=20261104135324.492692-1-herve.codina@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=andi.shyti@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel.machon@microchip.com \
--cc=horatiu.vultur@microchip.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=peda@lysator.liu.se \
--cc=robh@kernel.org \
--cc=saravanak@kernel.org \
--cc=steen.hegelund@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®