From: <markus.stockhausen@gmx.de>
To: "'Rob Herring'" <robh@kernel.org>
Cc: <andi.shyti@kernel.org>, <linux-i2c@vger.kernel.org>
Subject: AW: [PATCH 1/2] dt-bindings: i2c: Add i2c-shared-gpio
Date: Fri, 8 May 2026 16:43:23 +0200 [thread overview]
Message-ID: <007a01dcdef9$05ba7140$112f53c0$@gmx.de> (raw)
In-Reply-To: <20260508131830.GA1135235-robh@kernel.org>
> Von: Rob Herring <robh@kernel.org>
> Gesendet: Freitag, 8. Mai 2026 15:19
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Betreff: Re: [PATCH 1/2] dt-bindings: i2c: Add i2c-shared-gpio
> ...
> This is basically a mux, so you should leverage i2c-mux.yaml. Maybe
> there is driver infrastructure you can leverage too.
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.
Will address other feedbacks when direction is clear.
Markus
next prev parent reply other threads:[~2026-05-08 14:43 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 ` markus.stockhausen [this message]
2026-05-09 17:38 ` AW: " Wolfram Sang
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='007a01dcdef9$05ba7140$112f53c0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--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