From: Herve Codina <herve.codina@bootlin.com>
To: Ayush Singh <ayush@beagleboard.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree-spec@vger.kernel.org,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>
Subject: [PATCH v2 0/1] i2c: Introduce I2C bus extensions
Date: Wed, 30 Apr 2025 17:21:59 +0200 [thread overview]
Message-ID: <20250430152201.209797-1-herve.codina@bootlin.com> (raw)
Hi,
This is a resend of the series in order to continue discussion started
previously. In this resend, patch 2 previously available has been
removed (already applied).
An I2C bus can be wired to the connector and allows an add-on board to
connect additional I2C devices to this bus.
Those additional I2C devices could be described as sub-nodes of the I2C
bus controller node however for hotplug connectors described via device
tree overlays there is additional level of indirection, which is needed
to decouple the overlay and the base tree.
This decoupling is performed thanks to the I2C bus extension feature
which is introduced and detailed in patch 2 of this series.
The implementation related to I2C bus extension has been already
proposed as an RFC in Linux [0]. The missing part in this RFC was the
binding.
This binding related to I2C controller is not available in the Linux
repository but in dt-schema repository and so, this series update the
I2C controller binding to introduce the feature.
Compare to the previous iteration, patch 1 available in v1 has been
removed (already applied). No other modification has been done excep
adding a reviewed-by tag. Indeed conclusions were not reached in the
previous iteration discussion.
As a reminder, topics started in the v1 series discussion were the
following:
- i2c-bus-extension@0: usage of a subnode with unit address
- Presence of phandles in both direction (double linked list)
Best regards,
Hervé Codina
Changes v1 -> v2
v1: https://lore.kernel.org/all/20250401081041.114333-1-herve.codina@bootlin.com/
Patch 1 in v1:
Removed (already applied)
Patch 1 (2 in v1):
Add 'Reviewed-by: Ayush Singh <ayush@beagleboard.org>'
Herve Codina (1):
schemas: i2c: Introduce I2C bus extensions
dtschema/schemas/i2c/i2c-controller.yaml | 67 ++++++++++++++++++++++++
1 file changed, 67 insertions(+)
--
2.49.0
next reply other threads:[~2025-04-30 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 15:21 Herve Codina [this message]
2025-04-30 15:22 ` [PATCH v2 1/1] schemas: i2c: Introduce I2C bus extensions Herve Codina
2025-05-02 14:09 ` Luca Ceresoli
2025-05-05 8:22 ` 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=20250430152201.209797-1-herve.codina@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=ayush@beagleboard.org \
--cc=conor+dt@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).