From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Li Yang <leoli@freescale.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Gao Pan <b54642@freescale.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Wolfram Sang <wsa@the-dreams.de>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH] i2c: imx: make bus recovery through pinctrl optional
Date: Thu, 19 Nov 2015 09:08:22 +0100 [thread overview]
Message-ID: <20151119080822.GY22022@pengutronix.de> (raw)
In-Reply-To: <CADRPPNQZye7t2biS2Z8p3y7O6=xw4UcOLRC5ngs2Qvuh0UHXGg@mail.gmail.com>
Hello,
Cc += Linus Walleij, linux-gpio
On Wed, Nov 18, 2015 at 04:59:11PM -0600, Li Yang wrote:
> On Wed, Nov 18, 2015 at 1:24 AM, Uwe Kleine-König
> <u.kleine-koenig@pengutronix.de> wrote:
> > On Tue, Nov 17, 2015 at 06:02:59PM -0600, Li Yang wrote:
> >> @@ -1125,7 +1119,12 @@ static int i2c_imx_probe(struct platform_device *pdev)
> >> goto clk_disable;
> >> }
> >>
> >> - i2c_imx_init_recovery_info(i2c_imx, pdev);
> >> + /* optional bus recovery feature through pinctrl */
> >> + i2c_imx->pinctrl = devm_pinctrl_get(&pdev->dev);
> >> + if (IS_ERR_OR_NULL(i2c_imx->pinctrl))
> >> + dev_info(&pdev->dev, "can't get pinctrl, bus recovery feature disabled\n");
> >> + else
> >> + i2c_imx_init_recovery_info(i2c_imx, pdev);
> >
> > I'm pretty sure this is wrong. If pinctrl isn't available
> > devm_pinctrl_get returns NULL? But AFAIK you must not ignore an error,
> > so the better thing to do is:
>
> If CONFIG_PINCTRL is not enabled, the devm_pinctrl_get() will return
> NULL directly as defined in the include/linux/pinctrl/consumer.h.
>
> If CONFIG_PINCTRL is enabled because we are using a multi-platform
> image but the actual hardware used doesn't have a pinctrl driver or
> pinctrl device tree nodes. It is expected that the devm_pinctrl_get()
> will return error. But as the pinctrl is only used for bus recovery
> which is just an optional function of this driver. We shouldn't
> bailout the probe but keep the driver working without the bus recovery
> function. As for generic errors like (!dev) or out-of-memory, the
> probe will fail elsewhere anyway.
IMHO you shouldn't ignore -ENOMEM from devm_pinctrl_get but just the
case for "there was no pinctrl specified in dt". Also consider the i2c
driver is loaded before the pinctrl driver and devm_pinctrl_get returns
-EPROBE_DEFER (I assume it does, didn't check), this should be handled.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2015-11-19 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1447804979-29550-1-git-send-email-leoli@freescale.com>
[not found] ` <20151118072437.GS22022@pengutronix.de>
[not found] ` <CADRPPNQZye7t2biS2Z8p3y7O6=xw4UcOLRC5ngs2Qvuh0UHXGg@mail.gmail.com>
2015-11-19 8:08 ` Uwe Kleine-König [this message]
2015-11-20 18:04 ` [PATCH] i2c: imx: make bus recovery through pinctrl optional Li Yang
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=20151119080822.GY22022@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=b54642@freescale.com \
--cc=leoli@freescale.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-kernel@vger.kernel.org \
--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).