From: Jonathan Cameron <jic23@kernel.org>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Kevin Tsai <ktsai@capellamicro.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Linus Walleij <linus.walleij@linaro.org>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] iio: light: gp2ap002: Make use of the helper function dev_err_probe()
Date: Wed, 29 Sep 2021 17:08:02 +0100 [thread overview]
Message-ID: <20210929170802.1ab77b3a@jic23-huawei> (raw)
In-Reply-To: <20210928014156.1491-3-caihuoqing@baidu.com>
On Tue, 28 Sep 2021 09:41:54 +0800
Cai Huoqing <caihuoqing@baidu.com> wrote:
> When possible use dev_err_probe help to properly deal with the
> PROBE_DEFER error, the benefit is that DEFER issue will be logged
> in the devices_deferred debugfs file.
> Using dev_err_probe() can reduce code size, and the error value
> gets printed.
>
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
There is an explicit return of -EPROBE_DEFER in here that we should
probably also handle.
https://elixir.bootlin.com/linux/latest/source/drivers/iio/light/gp2ap002.c#L508
I guess simplest option is
return dev_err_probe(dev, -EPROBE_DEFER, "no ADC, deferring\n");
> ---
> drivers/iio/light/gp2ap002.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/iio/light/gp2ap002.c b/drivers/iio/light/gp2ap002.c
> index f960be7d4001..724a3928ead1 100644
> --- a/drivers/iio/light/gp2ap002.c
> +++ b/drivers/iio/light/gp2ap002.c
> @@ -521,15 +521,14 @@ static int gp2ap002_probe(struct i2c_client *client,
> }
>
> gp2ap002->vdd = devm_regulator_get(dev, "vdd");
> - if (IS_ERR(gp2ap002->vdd)) {
> - dev_err(dev, "failed to get VDD regulator\n");
> - return PTR_ERR(gp2ap002->vdd);
> - }
> + if (IS_ERR(gp2ap002->vdd))
> + return dev_err_probe(dev, PTR_ERR(gp2ap002->vdd),
> + "failed to get VDD regulator\n");
> +
> gp2ap002->vio = devm_regulator_get(dev, "vio");
> - if (IS_ERR(gp2ap002->vio)) {
> - dev_err(dev, "failed to get VIO regulator\n");
> - return PTR_ERR(gp2ap002->vio);
> - }
> + if (IS_ERR(gp2ap002->vio))
> + return dev_err_probe(dev, PTR_ERR(gp2ap002->vio),
> + "failed to get VIO regulator\n");
>
> /* Operating voltage 2.4V .. 3.6V according to datasheet */
> ret = regulator_set_voltage(gp2ap002->vdd, 2400000, 3600000);
next prev parent reply other threads:[~2021-09-29 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 1:41 [PATCH v2 1/4] iio: light: cm3605: Make use of the helper function dev_err_probe() Cai Huoqing
2021-09-28 1:41 ` [PATCH v2 2/4] iio: light: cm36651: " Cai Huoqing
2021-10-07 17:36 ` Jonathan Cameron
2021-09-28 1:41 ` [PATCH v2 3/4] iio: light: gp2ap002: " Cai Huoqing
2021-09-28 13:48 ` Linus Walleij
2021-09-29 16:08 ` Jonathan Cameron [this message]
2021-09-28 1:41 ` [PATCH v2 4/4] iio: light: noa1305: " Cai Huoqing
2021-10-07 17:38 ` Jonathan Cameron
2021-10-08 2:09 ` Cai Huoqing
2021-09-29 16:00 ` [PATCH v2 1/4] iio: light: cm3605: " Jonathan Cameron
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=20210929170802.1ab77b3a@jic23-huawei \
--to=jic23@kernel.org \
--cc=caihuoqing@baidu.com \
--cc=ktsai@capellamicro.com \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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