From: Ruan Jinjie <ruanjinjie@huawei.com>
To: "Yann Sionneau" <yann@sionneau.net>,
"Leo Li" <leoyang.li@nxp.com>,
"Codrin Ciubotariu" <codrin.ciubotariu@microchip.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Oleksij Rempel" <linux@rempel-privat.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>, "Wolfram Sang" <wsa@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux@armlinux.org.uk
Cc: <linux-gpio@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH -next v2] I2C: Fix return value check for devm_pinctrl_get()
Date: Fri, 18 Aug 2023 09:53:49 +0800 [thread overview]
Message-ID: <fe0d14a3-a890-8602-5be7-4e58ef0d8d1a@huawei.com> (raw)
In-Reply-To: <6b508343-7b7f-0fd5-d83f-92dc88a9510d@sionneau.net>
On 2023/8/18 7:07, Yann Sionneau wrote:
> Hi,
>
> Le 17/08/2023 à 19:30, Leo Li a écrit :
>
>>> The devm_pinctrl_get() function returns error pointers and never returns
>>> NULL. Update the checks accordingly.
>> Not exactly. It can return NULL when CONFIG_PINCTRL is not defined.
>> We probably should fix that API too.
>>
>> include/linux/pinctrl/consumer.h:
>> static inline struct pinctrl * __must_check devm_pinctrl_get(struct
>> device *dev)
>> {
>> return NULL;
>> }
>
> So, as Leo pointed out it seems devm_pinctrl_get() can in fact return
> NULL, when CONFIG_PINCTRL is not defined.
>
> What do we do about this?
>
> Proposals:
>
> 1/ make sure all call sites of devm_pinctrl_get() do check for error
> with IS_ERR *and* check for NULL => therefore using IS_ERR_OR_NULL
I think it's the best.
>
> 2/ change the fallback implementation in
> include/linux/pinctrl/consumer.h to return ERR_PTR(-Esomething) (which
> errno?)
It seems a convention to return NULL if the related macro is not defined.
>
> 3/ another solution?
Make I2C_IMX and I2C_AT91 config depends on PINCTRL config is another
option. However it seems that the function call devm_pinctrl_get() has
an optional recovery feature from the following notes and dev_info(). So
this dependency is not necessary.
1378 /*
1379 * We switch SCL and SDA to their GPIO function and do some bitbanging
1380 * for bus recovery. These alternative pinmux settings can be
1381 * described in the device tree by a separate pinctrl state "gpio". If
1382 * this is missing this is not a big problem, the only implication is
1383 * that we can't do bus recovery.
1384 */
1385 static int i2c_imx_init_recovery_info(struct imx_i2c_struct *i2c_imx,
1386 struct platform_device *pdev)
1387 {
1388 struct i2c_bus_recovery_info *rinfo = &i2c_imx->rinfo;
1389
1390 i2c_imx->pinctrl = devm_pinctrl_get(&pdev->dev);
828 static int at91_init_twi_recovery_gpio(struct platform_device *pdev,
829 struct at91_twi_dev *dev)
830 {
831 struct i2c_bus_recovery_info *rinfo = &dev->rinfo;
832
833 rinfo->pinctrl = devm_pinctrl_get(&pdev->dev);
834 if (!rinfo->pinctrl || IS_ERR(rinfo->pinctrl)) {
835 dev_info(dev->dev, "can't get pinctrl, bus recovery not
supported\n");
836 return PTR_ERR(rinfo->pinctrl);
837 }
>
> Regards,
>
next prev parent reply other threads:[~2023-08-18 1:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 2:20 [PATCH -next v2] I2C: Fix return value check for devm_pinctrl_get() Ruan Jinjie
2023-08-17 4:38 ` Oleksij Rempel
2023-08-17 6:58 ` Linus Walleij
2023-08-17 16:01 ` Nicolas Ferre
2023-08-17 17:30 ` Leo Li
2023-08-17 23:07 ` Yann Sionneau
2023-08-18 1:53 ` Ruan Jinjie [this message]
2023-08-18 5:32 ` Sascha Hauer
2023-08-18 7:18 ` Linus Walleij
2023-08-18 7:27 ` Ruan Jinjie
2023-08-18 2:47 ` Ruan Jinjie
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=fe0d14a3-a890-8602-5be7-4e58ef0d8d1a@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=codrin.ciubotariu@microchip.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux@armlinux.org.uk \
--cc=linux@rempel-privat.de \
--cc=nicolas.ferre@microchip.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa@kernel.org \
--cc=yann@sionneau.net \
/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