From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Li Yang <leoyang.li@nxp.com>
Cc: Gao Pan <pandy.gao@nxp.com>, Wolfram Sang <wsa@the-dreams.de>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5] i2c: imx: make bus recovery through pinctrl optional
Date: Tue, 6 Sep 2016 20:58:49 +0200 [thread overview]
Message-ID: <20160906185849.27pjhawadca5pwow@pengutronix.de> (raw)
In-Reply-To: <1471644322-22670-1-git-send-email-leoyang.li@nxp.com>
On Fri, Aug 19, 2016 at 05:05:22PM -0500, Li Yang wrote:
> Since commit 1c4b6c3bcf30 ("i2c: imx: implement bus recovery") the
> driver starts to use gpio/pinctrl to do i2c bus recovery. But pinctrl
> is not always available for platforms with this controller such as ls1021a
> and ls1043a, and the device tree binding also mentioned this gpio based
> recovery mechanism as optional. The patch makes it really optional that
> the probe function won't bailout but just disable the bus recovery function
> when pinctrl is not available.
>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
> Cc: Gao Pan <pandy.gao@nxp.com>
> Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> v5:
> Revert the last minute change of recovery info initialization timing, it
> will cause problem if initialized after i2c_add_numbered_adapter()
>
> v4:
> Remove the use of IS_ERR_OR_NULL
> Move the condition judgement to i2c_imx_init_recovery_info()
> Change the timing of recovery initialization to be after bus registration
>
> v3:
> Rebased to Wolfram's for-next branch
> Added acked-by from Linus Walleij
> Update to use new nxp email addresses due to company merge
>
> drivers/i2c/busses/i2c-imx.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
> index 1844bc9..7ae7992 100644
> --- a/drivers/i2c/busses/i2c-imx.c
> +++ b/drivers/i2c/busses/i2c-imx.c
> @@ -989,6 +989,15 @@ static void i2c_imx_init_recovery_info(struct imx_i2c_struct *i2c_imx,
> {
> struct i2c_bus_recovery_info *rinfo = &i2c_imx->rinfo;
>
> + /* if pinctrl is not supported on the system */
> + if (IS_ERR(i2c_imx->pinctrl))
> + i2c_imx->pinctrl = NULL;
> +
> + if (!i2c_imx->pinctrl) {
> + dev_info(&pdev->dev, "can't get pinctrl, bus recovery not supported\n");
> + return;
> + }
> +
> i2c_imx->pinctrl_pins_default = pinctrl_lookup_state(i2c_imx->pinctrl,
> PINCTRL_STATE_DEFAULT);
> i2c_imx->pinctrl_pins_gpio = pinctrl_lookup_state(i2c_imx->pinctrl,
> @@ -1081,8 +1090,11 @@ static int i2c_imx_probe(struct platform_device *pdev)
> return ret;
> }
>
> + /* optional bus recovery feature through pinctrl */
> i2c_imx->pinctrl = devm_pinctrl_get(&pdev->dev);
> - if (IS_ERR(i2c_imx->pinctrl)) {
> + /* bailout on -ENOMEM or -EPROBE_DEFER, continue for other errors */
> + if (PTR_ERR(i2c_imx->pinctrl) == -ENOMEM ||
> + PTR_ERR(i2c_imx->pinctrl) == -EPROBE_DEFER) {
> ret = PTR_ERR(i2c_imx->pinctrl);
> goto clk_disable;
> }
devm_pinctrl_get might return the following error-valued pointers:
- -EINVAL
- -ENOMEM
- -ENODEV
- -EPROBE_DEFER
There are several error paths returning -EINVAL, one is when an invalid
phandle is used. Do you really want to ignore that?
IMO error handling is better done with inverse logic, that is continue
on some explicit error, bail out on all unknown stuff. This tends to be
more robust. Also the comment should be improved to not explain that for
-ENOMEM and -EPROBE_DEFER we bail out (which should be obvious for
anyone who can read C) but to explain why.
Also I'd put
i2c_imx->pinctrl = NULL;
directly after devm_pinctrl_get() which I consider the more obvious
place for this.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2016-09-06 18:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 22:05 [PATCH v5] i2c: imx: make bus recovery through pinctrl optional Li Yang
2016-09-06 18:58 ` Uwe Kleine-König [this message]
2016-09-06 20:06 ` Leo Li
2016-09-06 21:07 ` Uwe Kleine-König
2016-09-06 23:14 ` Leo Li
2016-09-06 21:51 ` Stefan Agner
2016-09-06 22:40 ` Leo Li
[not found] ` <CAChUvXOGjTn6K5588UVgjbRWUY+weDtk2qbOU-NM4=kA2znh=Q@mail.gmail.com>
2016-09-07 5:55 ` Uwe Kleine-König
[not found] ` <CAChUvXMPDZB7=ZArQ5+6ae42N=Bsgv_OczGXnyhBjEdjt_yvsw@mail.gmail.com>
2016-09-07 16:40 ` Leo Li
2016-09-12 16:35 ` Leo Li
2016-09-12 18:29 ` Leo Li
2016-09-08 22:39 ` Stefan Agner
2016-09-08 23:57 ` Leo Li
2016-09-09 16:51 ` Stefan Agner
2016-09-09 19:37 ` Leo Li
2016-09-09 20:34 ` Stefan Agner
2016-09-09 20:59 ` Uwe Kleine-König
2016-09-12 16:47 ` Leo Li
2016-09-12 8:21 ` Lothar Waßmann
2016-09-12 16:27 ` Leo Li
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=20160906185849.27pjhawadca5pwow@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pandy.gao@nxp.com \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).