Devicetree
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: markus.stockhausen@gmx.de, andi.shyti@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: Re: AW: [PATCH v2 0/2] i2c: Add i2c-shared-gpio driver
Date: Wed, 13 May 2026 09:47:50 +0200	[thread overview]
Message-ID: <agQspjVCkbmVDnt_@shikoro> (raw)
In-Reply-To: <CAMRc=MddGonpdukfZ_eHa8C4ysdCTqhYva6yVRue06LVkyubxg@mail.gmail.com>

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

Hi Bart,

> Yes, in that case it seems to me it needs a separate virtual device
> driving it. In general, the idea Markus presented is fine but it must
> not be described in DT. Instead, you need to create an auxiliary
> device from subsystem code.

Okay, I get it that it should not be described in DT. DT should only
have standard i2c-gpio busses and the OS needs to figure the details,
right?

I wonder about the subsystem involvement, though. The I2C core doesn't
care about the scl-gpios property (except for GPIO recovery which is
moot with the i2c-gpio driver). So, maybe this should be handled in the
i2c-gpio driver instead?

All the best,

   Wolfram


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

  reply	other threads:[~2026-05-13  7:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 16:25 [PATCH v2 0/2] i2c: Add i2c-shared-gpio driver Markus Stockhausen
2026-05-11 16:25 ` [PATCH v2 1/2] dt-bindings: i2c: Add i2c-shared-gpio Markus Stockhausen
2026-05-11 17:36   ` Rob Herring (Arm)
2026-05-12 20:59   ` sashiko-bot
2026-05-11 16:25 ` [PATCH v2 2/2] i2c: Add driver for gpio based busses with shared SCL Markus Stockhausen
2026-05-12 21:44   ` sashiko-bot
2026-05-12 11:00 ` [PATCH v2 0/2] i2c: Add i2c-shared-gpio driver Bartosz Golaszewski
2026-05-13  5:33   ` AW: " markus.stockhausen
2026-05-13  7:12     ` Wolfram Sang
2026-05-13  7:26       ` Bartosz Golaszewski
2026-05-13  7:47         ` Wolfram Sang [this message]
2026-05-13  7:50           ` Bartosz Golaszewski
2026-05-13 12:11   ` Rob Herring
2026-05-13 12:25     ` AW: " 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=agQspjVCkbmVDnt_@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=andi.shyti@kernel.org \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --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