public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
	Herve Codina <herve.codina@bootlin.com>,
	Luca Ceresoli <luca@lucaceresoli.net>
Cc: "Andi Shyti" <andi.shyti@kernel.org>,
	"Rob Herring" <robh@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] i2c: muxes: Add GPIO-detected hotplug I2C
Date: Mon, 15 Sep 2025 13:35:40 +0200	[thread overview]
Message-ID: <aMf6DLr8pTCP8tKn@shikoro> (raw)
In-Reply-To: <20250915060141.12540-1-clamor95@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

On Mon, Sep 15, 2025 at 09:01:36AM +0300, Svyatoslav Ryhel wrote:
> Implement driver for hot-plugged I2C busses, where some devices on
> a bus are hot-pluggable and their presence is indicated by GPIO line.
> This feature is used by the ASUS Transformers family, by the  Microsoft
> Surface RT/2 and maybe more.
> 
> ASUS Transformers expose i2c line via proprietary 40 pin plug and wire
> that line through optional dock accessory. Devices in the dock are
> connected to this i2c line and docks presence is detected by a dedicted
> GPIO.
> 
> Michał Mirosław (1):
>   i2c: muxes: Add GPIO-detected hotplug I2C
> 
> Svyatoslav Ryhel (1):
>   dt-bindings: i2c: Document GPIO detected hot-plugged I2C bus
> 
>  .../bindings/i2c/i2c-hotplug-gpio.yaml        |  65 +++++
>  drivers/i2c/muxes/Kconfig                     |  11 +
>  drivers/i2c/muxes/Makefile                    |   1 +
>  drivers/i2c/muxes/i2c-hotplug-gpio.c          | 263 ++++++++++++++++++
>  4 files changed, 340 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/i2c/i2c-hotplug-gpio.yaml
>  create mode 100644 drivers/i2c/muxes/i2c-hotplug-gpio.c

Adding Herve and Luca to CC because they want to achieve the same with
their I2C bus extensions, no?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2025-09-15 11:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15  6:01 [PATCH v1 0/2] i2c: muxes: Add GPIO-detected hotplug I2C Svyatoslav Ryhel
2025-09-15  6:01 ` [PATCH v1 1/2] dt-bindings: i2c: Document GPIO detected hot-plugged I2C bus Svyatoslav Ryhel
2025-09-15  6:01 ` [PATCH v1 2/2] i2c: muxes: Add GPIO-detected hotplug I2C Svyatoslav Ryhel
2025-09-15 11:35 ` Wolfram Sang [this message]
2025-09-15 11:53   ` [PATCH v1 0/2] " Svyatoslav Ryhel
2025-09-15 15:42     ` Wolfram Sang
2025-09-16  6:19       ` Herve Codina
2025-09-16  7:50         ` Luca Ceresoli
2025-09-16  8:11           ` Svyatoslav Ryhel

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=aMf6DLr8pTCP8tKn@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=andi.shyti@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=herve.codina@bootlin.com \
    --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 \
    /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