From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Esben Haabendal <esben@geanix.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org,
Gregor Herburger <gregor.herburger@ew.tq-group.com>,
linux-i2c@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
linux-arm-kernel@lists.infradead.org,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [PATCH] i2c: imx: move to generic GPIO recovery
Date: Fri, 26 Jan 2024 08:43:15 +0100 [thread overview]
Message-ID: <20240126074315.GE381737@pengutronix.de> (raw)
In-Reply-To: <875xzgh7dr.fsf@geanix.com>
On Fri, Jan 26, 2024 at 08:38:08AM +0100, Esben Haabendal wrote:
> Oleksij Rempel <o.rempel@pengutronix.de> writes:
>
> > ....
> >> + struct i2c_bus_recovery_info *bri = &i2c_imx->rinfo;
> >>
> >> - dev_dbg(&pdev->dev, "using scl%s for recovery\n",
> >> - rinfo->sda_gpiod ? ",sda" : "");
> >> + bri->pinctrl = devm_pinctrl_get(&pdev->dev);
> >> + if (IS_ERR(bri->pinctrl))
> >> + return PTR_ERR(bri->pinctrl);
> >
> > According to the commit message - "pinctrl becomes optional", but this
> > code stops probe if pinctrl will fail for one or another reason. I do
> > not see any place returning NULL on fail. Do I'm missing something?
>
> The caller, i2c_imx_probe(), does only check for -EPROBE_DEFER, and
> simply ignores any other error codes.
>
> I assume it is on purpose, so any problems with initializing i2c
> recovery does not cause complete failure of the i2c controller, which
> seems sane to me.
Good point, this is what I overlooked :)
Acked-by: Oleksij Rempel <o.rempel@pengutronix.de>
Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-01-26 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 13:56 [PATCH] i2c: imx: move to generic GPIO recovery Esben Haabendal
2024-01-26 6:07 ` Oleksij Rempel
2024-01-26 7:38 ` Esben Haabendal
2024-01-26 7:43 ` Oleksij Rempel [this message]
2024-01-31 0:18 ` Andi Shyti
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=20240126074315.GE381737@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=alexander.stein@ew.tq-group.com \
--cc=andi.shyti@kernel.org \
--cc=esben@geanix.com \
--cc=festevam@gmail.com \
--cc=gregor.herburger@ew.tq-group.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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