From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Yann Sionneau <ysionneau@kalray.eu>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Julian Vetter <jvetter@kalrayinc.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] Currently if the SoC needs pinctrl to switch the SCL and SDA from the I2C function to GPI
Date: Tue, 22 Aug 2023 16:35:48 +0300 [thread overview]
Message-ID: <20230822133548.GO3465@black.fi.intel.com> (raw)
In-Reply-To: <ZOS3cI7RL443mizj@smile.fi.intel.com>
On Tue, Aug 22, 2023 at 04:26:08PM +0300, Andy Shevchenko wrote:
> On Tue, Aug 22, 2023 at 03:11:23PM +0200, Yann Sionneau wrote:
> > scl-gpio = <>;
> > sda-gpio = <>;
> >
> > Are not enough for some SoCs to have a working recovery.
> > Some need:
> >
> > scl-gpio = <>;
> > sda-gpio = <>;
> > pinctrl-names = "default", "recovery";
> > pinctrl-0 = <&i2c_pins_hw>;
> > pinctrl-1 = <&i2c_pins_gpio>;
> >
> > The driver was not filling rinfo->pinctrl with the device node
> > pinctrl data which is needed by generic recovery code.
> >
> > Signed-off-by: Yann Sionneau <ysionneau@kalray.eu>
> > ---
> > V3 -> V4:
> > * Replace `else if` by simply `if`.
>
> You forgot my tag. Why?
> Also I think this will generate more code and more noise in debug case.
> So, I admit I gave a bad suggestion in previous round.
>
> Please, go for v3 with my tag (as v5).
While there fix $subject to follow the convention used in the driver.
next prev parent reply other threads:[~2023-08-22 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 13:11 [PATCH v4] Currently if the SoC needs pinctrl to switch the SCL and SDA from the I2C function to GPI Yann Sionneau
2023-08-22 13:26 ` Andy Shevchenko
2023-08-22 13:35 ` Mika Westerberg [this message]
2023-08-22 14:15 ` Yann Sionneau
2023-08-22 14:27 ` Andy Shevchenko
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=20230822133548.GO3465@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jvetter@kalrayinc.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ysionneau@kalray.eu \
/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