Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: markus.stockhausen@gmx.de, Bartosz Golaszewski <brgl@kernel.org>
Cc: 'Rob Herring' <robh@kernel.org>,
	andi.shyti@kernel.org, linux-i2c@vger.kernel.org
Subject: Re: AW: [PATCH 1/2] dt-bindings: i2c: Add i2c-shared-gpio
Date: Sat, 9 May 2026 19:38:34 +0200	[thread overview]
Message-ID: <af9xGlIWG_OmREzX@shikoro> (raw)
In-Reply-To: <007a01dcdef9$05ba7140$112f53c0$@gmx.de>

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

Hi all,

> Thats what I broke my head about the most. From testing and
> my little knowledge I came to the conclusion 
> 
> - two native i2c-gpio based busses can not share the same SCL
> - so mux infrastructure cannot build on top of that
> 
> But maybe some I2C expert can advise.

I am not sure i2c-mux is the right approach here. Because every SDA is
already wired, there is no need to select/deselect something. It is only
that SCL is shared, right?

Now, the GPIO subsystem since recently allows for shared GPIOs[1]. This
sounds like the proper approach to me. Sadly, I can't help much because
I have not used this API so far. So, it seems you rather need a GPIO
expert... CCing Bart.

@Bart: is it possible to share a GPIO so that multiple i2c-gpio
instances can use the same GPIO as SCL? Use case is explained in the
cover letter[2].

Happy hacking,

   Wolfram


[1] https://lwn.net/Articles/1044022/
[2] https://lore.kernel.org/r/20260507181711.2696783-1-markus.stockhausen@gmx.de

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

  reply	other threads:[~2026-05-09 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 18:17 [PATCH 0/2] i2c: Add i2c-shared-gpio driver Markus Stockhausen
2026-05-07 18:17 ` [PATCH 1/2] dt-bindings: i2c: Add i2c-shared-gpio Markus Stockhausen
2026-05-07 19:30   ` Rob Herring (Arm)
2026-05-08 13:18   ` Rob Herring
2026-05-08 14:43     ` AW: " markus.stockhausen
2026-05-09 17:38       ` Wolfram Sang [this message]
2026-05-09 20:41         ` AW: " markus.stockhausen
2026-05-11 12:43           ` Bartosz Golaszewski
2026-05-11 15:39             ` Wolfram Sang
2026-05-11 16:08               ` Bartosz Golaszewski
2026-05-13 16:21         ` Rob Herring
2026-05-13 17:19           ` AW: " markus.stockhausen
2026-05-13 21:34             ` 'Wolfram Sang'
2026-05-09 11:16     ` markus.stockhausen
2026-05-07 18:17 ` [PATCH 2/2] i2c: shared-gpio: Add driver for gpio based busses with shared SCL Markus Stockhausen

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=af9xGlIWG_OmREzX@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=andi.shyti@kernel.org \
    --cc=brgl@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=markus.stockhausen@gmx.de \
    --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