From: Herve Codina <herve.codina@bootlin.com>
To: Ayush Singh <ayush@beagleboard.org>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, luca.ceresoli@bootlin.com,
robh@kernel.org, thomas.petazzoni@bootlin.com,
wsa+renesas@sang-engineering.com
Subject: Re: [RFC PATCH 0/3] i2c: Introduce i2c bus extensions
Date: Fri, 13 Jun 2025 09:30:16 +0200 [thread overview]
Message-ID: <20250613093016.43230e3b@bootlin.com> (raw)
In-Reply-To: <525877c8-6c64-45b3-b4aa-a52768e59b86@beagleboard.org>
Hi Ayush,
On Thu, 12 Jun 2025 13:22:45 +0530
Ayush Singh <ayush@beagleboard.org> wrote:
> I have tested this patch series for use with pocketbeagle 2 connector
> driver [0]. To get a better idea how it looks in real devicetree, see
> the base tree [1] and the overlay [2]. Since it also used gpio and pwm
> nexus nodes, along with providing pinmux for pins, it can provide a
> better picture of how the different pieces (export-symbols, nexus nodes,
> etc) look when combined.
Nice. Happy to see that I am no more alone with a system using these
features.
>
>
> I also have a question for Herve. Do you already have any working
> patches for similar extension for SPI and UART in some private tree?
No, I didn't do anything related to SPI nor UART.
On my system, no SPI nor UART are wired to my connector and so, I haven't
got any needs to implement extension busses for SPI an UART (serial dev bus)
nor any support for nexus nodes for other kind of components.
Best regards,
Hervé
next prev parent reply other threads:[~2025-06-13 7:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 17:39 [RFC PATCH 0/3] i2c: Introduce i2c bus extensions Herve Codina
2025-02-05 17:39 ` [RFC PATCH 1/3] i2c: core: Follow i2c-parent when retrieving an adapter from node Herve Codina
2025-04-03 9:03 ` Wolfram Sang
2025-04-03 10:50 ` Herve Codina
2025-04-03 11:20 ` Wolfram Sang
2025-04-03 12:21 ` Herve Codina
2025-02-05 17:39 ` [RFC PATCH 2/3] i2c: i2c-core-of: Move children registration in a dedicated function Herve Codina
2025-04-03 9:07 ` Wolfram Sang
2025-04-03 10:51 ` Herve Codina
2025-02-05 17:39 ` [RFC PATCH 3/3] i2c: i2c-core-of: Handle i2c bus extensions Herve Codina
2025-02-12 5:54 ` Krzysztof Kozlowski
2025-02-12 9:45 ` Herve Codina
2025-04-03 9:09 ` Wolfram Sang
2025-02-19 13:38 ` [RFC PATCH 0/3] i2c: Introduce " Herve Codina
2025-03-20 12:49 ` Wolfram Sang
2025-03-20 16:31 ` Luca Ceresoli
2025-03-20 21:37 ` Wolfram Sang
2025-04-03 9:15 ` Wolfram Sang
2025-06-12 7:52 ` Ayush Singh
2025-06-13 7:30 ` Herve Codina [this message]
2025-07-03 11:26 ` Ayush Singh
2025-07-03 15:19 ` 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=20250613093016.43230e3b@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=ayush@beagleboard.org \
--cc=conor+dt@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).