From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: "'Bartosz Golaszewski'" <brgl@kernel.org>,
<wsa+renesas@sang-engineering.com>, <andi.shyti@kernel.org>,
<linusw@kernel.org>
Cc: <linux-i2c@vger.kernel.org>, <linux-gpio@vger.kernel.org>
Subject: AW: [PATCH v3] i2c: i2c-gpio: Enhance driver for buses with shared SCL
Date: Mon, 25 May 2026 18:08:00 +0200 [thread overview]
Message-ID: <00c601dcec60$a9496f90$fbdc4eb0$@gmx.de> (raw)
In-Reply-To: <CAMRc=Mf6EQDF-fSVb+jhmLvMUi2eJ5QhukKC08S-T12HKinibw@mail.gmail.com>
Hi all,
> Von: Bartosz Golaszewski <brgl@kernel.org>
> Gesendet: Donnerstag, 21. Mai 2026 10:59
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Betreff: Re: [PATCH v3] i2c: i2c-gpio: Enhance driver for buses with shared SCL
> ...
> > /*
> > * Toggle SDA by changing the output value of the pin. This is only
> > * valid for pins configured as open drain (i.e. setting the value @@
> > -53,7 +72,7 @@ static void i2c_gpio_setscl_val(void *data, int state)
> > {
> > struct i2c_gpio_private_data *priv = data;
> >
> > - gpiod_set_value_cansleep(priv->scl, state);
> > + gpiod_set_value_cansleep(priv->scl->gpio, state);
>
> That one bothers me a bit. We're driving a clock line but may
> end up sleeping? That doesn't sound right. We typically do:
>
> setscl();
> udelay();
>
> I know it's been like this before and maybe I'm not understanding
> the whole picture so feel free to disregard the comment.
ATM I can only ignore that because I have no idea what this code
is about. Maybe soneone in CC can advise how to handle Bartosz's
question.
> Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Thanks for that.
Markus
next prev parent reply other threads:[~2026-05-25 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 17:31 [PATCH v3] i2c: i2c-gpio: Enhance driver for buses with shared SCL Markus Stockhausen
2026-05-20 18:44 ` Sander Vanheule
2026-05-21 8:59 ` Bartosz Golaszewski
2026-05-25 16:08 ` Markus Stockhausen [this message]
2026-05-27 10:24 ` Linus Walleij
2026-06-16 18:52 ` 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='00c601dcec60$a9496f90$fbdc4eb0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=andi.shyti@kernel.org \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.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.