Devicetree
 help / color / mirror / Atom feed
From: <markus.stockhausen@gmx.de>
To: "'Rob Herring'" <robh@kernel.org>,
	"'Bartosz Golaszewski'" <brgl@kernel.org>
Cc: <wsa+renesas@sang-engineering.com>, <andi.shyti@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: AW: [PATCH v2 0/2] i2c: Add i2c-shared-gpio driver
Date: Wed, 13 May 2026 14:25:11 +0200	[thread overview]
Message-ID: <036001dce2d3$8b65be70$a2313b50$@gmx.de> (raw)
In-Reply-To: <20260513121135.GA432696-robh@kernel.org>

> Von: Rob Herring <robh@kernel.org> 
> Gesendet: Mittwoch, 13. Mai 2026 14:12
> Betreff: Re: [PATCH v2 0/2] i2c: Add i2c-shared-gpio driver
> ...
> > > So the implementation manages several classic bitbang buses with
> > > locking/unlocking in the pre_xfer/post_xfer handlers.
> > >
> > > Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
> > >
> > 
> > Hi!
> > 
> > A couple high-level issues. You'll soon hear from the DT maintainers
> > and they'll ask if the i2c-shared-gpio compatible corresponds with an
> > actual piece of hardware on the board. It does not, so the bindings
> > will be rejected.
>
> Perhaps you missed I've already commented on this. I'm actually fine 
> with the binding at a high level.
>
> But if we want to model it as N i2c-gpio nodes I'm fine with that as 
> well.

Thanks for all your feedback on this. If it helps the dts and the end 
user I can offer to convert the driver into a simple drop-in replacement 
for i2c-gpio. Enhancing the existing i2c-gpio driver is beyond my
current knowledge.

Markus


      reply	other threads:[~2026-05-13 12:25 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
2026-05-13  7:50           ` Bartosz Golaszewski
2026-05-13 12:11   ` Rob Herring
2026-05-13 12:25     ` markus.stockhausen [this message]

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='036001dce2d3$8b65be70$a2313b50$@gmx.de' \
    --to=markus.stockhausen@gmx.de \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox