mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herve Codina <herve.codina@bootlin.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "Svyatoslav Ryhel" <clamor95@gmail.com>,
	"Rob Herring" <robh@kernel.org>,
	"Luca Ceresoli" <luca@lucaceresoli.net>,
	"Andi Shyti" <andi.shyti@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Peter Rosin" <peda@axentia.se>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Jonas Schwöbel" <jonasschwoebel@yahoo.de>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2 RESEND] i2c: muxes: Add GPIO-detected hotplug I2C
Date: Wed, 18 Nov 2026 14:10:28 +0100	[thread overview]
Message-ID: <20261118141028.24179f5c@bootlin.com> (raw)
In-Reply-To: <av2Nb_likDLz1u2c@shikoro>

On Wed, 18 Nov 2026 12:35:15 +0100
Wolfram Sang <wsa+renesas@sang-engineering.com> wrote:

> Hi Svyatoslav, and Hervé, and all,
> 
> > > > > > So, if you want upstream supported I2C hot-plugging, you need to wait
> > > > > > for Luca's and Herve's work being accepted. Or provide a superior
> > > > > > solution. Or, if you want, join the ride. You already have experience in
> > > > > > this field (and hardware plus use case), you would be a very welcome
> > > > > > contributor, I would say.  
> > > > >
> > > > > Agreed.
> > > > >
> > > > > What really slows things down is when there is only 1 user of a new
> > > > > binding. Too many times have I accepted one only for the 2nd user to
> > > > > show up right after accepting it and wanting something different. So
> > > > > now I just require more than 1 user and it is on the submitter(s) to do
> > > > > that. After all, it is their itch, not mine.  
> 
> For completeness, let me emphasize the above paragraphs again.
> 
> > > No new advancements. I moved on a prerequisite: Having support for addon
> > > format in dtb in order to have support for a list of exported symbols
> > > resolution when an dtb is applied on a live devicetree.  
> 
> Well, I would consider advancements in prerequisites also advancements.
> 
> > > Anyway, the v3 series [1] need to be updated and a new iteration need to be
> > > sent. Also, same operations need to be done on the SPI version [2].  
> 
> Hervé, is that the next planned step or are there prerequisites needed
> still?

I think this is a planned step. Is it the next one, I don't know.

Support for addon dtb format is a huge topic and I need to move forward on this
topic before switching back to i2c-bus-extension.

Even if we could avoid the need for i2c-bus-extension for I2C with addons, IHMO
decoupling things and having devices that belong on a extension board clearly
identified in a devicetree is a good thing to keep, i2c-bus-extension provides
this decoupling.

On SPI, no way to do without a spi-bus-extension. Chip selects must be translated
between chip select numbers provided by a base board SPI bus, wired to the connector
and chip select numbers seen from the extension board (i.e. chip select numbers at
connector level).

Having extension bus for both I2C and SPI make sense and keep things consistent
between both busses.

Working on extension busses can be done without addon dtb feature. I am just
too busy to work on both topics in parallel.

Best regards,
Hervé

> 
> > Rob, Wolfram, since the DT Addon framework is not mature yet, may
> > i2c-hotplug-gpio be accepted in some form? Maybe a staging driver or  
> 
> I vote against it. Accepting intermediate solutions will slow down the
> proper solution even more.
> 
> > with notes that ABI may be changed and are unstable or maybe as a
> > device specific driver only for transformers like
> > "asus-transformer-dock" etc?  
> 
> Which kernel are you using? Can't you use your driver downstream instead
> of upstream unless Herve's work is usable?
> 
> Happy hacking,
> 
>    Wolfram
> 



-- 
Hervé Codina, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2026-11-18 13:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13  6:00 Svyatoslav Ryhel
2025-10-13  6:00 ` [PATCH v1 1/2 RESEND] dt-bindings: i2c: Document GPIO detected hot-plugged I2C bus Svyatoslav Ryhel
2025-10-13  6:00 ` [PATCH v1 2/2 RESEND] i2c: muxes: Add GPIO-detected hotplug I2C Svyatoslav Ryhel
2025-10-15 22:50 ` [PATCH v1 0/2 " Andi Shyti
2025-10-16  7:00   ` Svyatoslav Ryhel
2025-10-16  7:32     ` Wolfram Sang
2025-10-17 10:29       ` Andi Shyti
2025-10-21 13:25       ` Rob Herring
2026-10-17 17:17         ` Svyatoslav Ryhel
2026-11-18  8:13           ` Herve Codina
2026-11-18  8:40             ` Svyatoslav Ryhel
2026-11-18 11:35               ` Wolfram Sang
2026-11-18 11:44                 ` Svyatoslav Ryhel
2026-11-18 11:52                   ` Wolfram Sang
2026-11-18 12:05                     ` Wolfram Sang
2026-11-18 13:10                 ` Herve Codina [this message]
2025-10-16  7:11   ` 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=20261118141028.24179f5c@bootlin.com \
    --to=herve.codina@bootlin.com \
    --cc=andi.shyti@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonasschwoebel@yahoo.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca@lucaceresoli.net \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=peda@axentia.se \
    --cc=robh@kernel.org \
    --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®