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

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

Hi Markus,

> 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?

I agree and it matches the idea of DT being for HW description only...

> Coming back to my offer about the new I2C bus that only 
> switches from compatible "i2c-gpio" to "i2c-gpio-shared". 

... even so far that I don't think we should use "i2c-gpio-shared" but
only "i2c-gpio". The DT part (HW description only) is this compatible
with SCL and SDA described. It is up to the OS to decide how to handle
multiple SCLs using the same pin...

> 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

... which should mean for Linux that the i2c-gpio driver recognizes an
already selected pin and reuses it by some reference.

> That will need no shared gpio features. Managing the list 
> should add ~100 lines and the rest of the driver can be 
> reused/adapted.

I think we are aligned. It would require no DT updates, only extra
handling in the i2c-gpio driver.

Bart, what do you think?

All the best,

   Wolfram


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

  reply	other threads:[~2026-05-13 21:34 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           ` AW: " markus.stockhausen
2026-05-13 21:34             ` 'Wolfram Sang' [this message]
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=agTuVxMAhttk9sX-@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