From: <markus.stockhausen@gmx.de>
To: "'Rob Herring'" <robh@kernel.org>,
"'Wolfram Sang'" <wsa+renesas@sang-engineering.com>
Cc: "'Bartosz Golaszewski'" <brgl@kernel.org>,
<andi.shyti@kernel.org>, <linux-i2c@vger.kernel.org>
Subject: AW: AW: [PATCH 1/2] dt-bindings: i2c: Add i2c-shared-gpio
Date: Wed, 13 May 2026 19:19:09 +0200 [thread overview]
Message-ID: <05b601dce2fc$9c82dc50$d58894f0$@gmx.de> (raw)
In-Reply-To: <CAL_Jsq+RyLno6kojsULC9M-Db+h1N+aoyJZgYs8nXtY4J+zEFw@mail.gmail.com>
> Von: Rob Herring <robh@kernel.org>
> Gesendet: Mittwoch, 13. Mai 2026 18:21
> An: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Betreff: Re: AW: [PATCH 1/2] dt-bindings: i2c: Add i2c-shared-gpio
> > ...
> > 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?
>
> There's no physical select, but it's still only 1 active at any time just like a mux.
While working around this challenge my POV is as follows:
- See each SDA/SCL combination as an always hardwired bus
- There is no muxing of the bus as a whole.
- It is only a question at what time access is allowed
- Why not expose each bus as simple as possible?
Coming back to my offer about the new I2C bus that only
switches from compatible "i2c-gpio" to "i2c-gpio-shared".
This should be achievable in the driver as follows:
- add each SDA to the individual bus
- build up a shared SCL list for all buses
- link each bus to the required SCL
That will need no shared gpio features. Managing the list
should add ~100 lines and the rest of the driver can be
reused/adapted.
Ideas, hints, objections?
Markus
next prev parent reply other threads:[~2026-05-13 17:19 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
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 ` markus.stockhausen [this message]
2026-05-13 21:34 ` AW: " '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='05b601dce2fc$9c82dc50$d58894f0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=andi.shyti@kernel.org \
--cc=brgl@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.