From: Mickael GUENE <mickael.guene@st.com>
To: Chuhong Yuan <hslester96@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: st-mipid02: add a check for devm_gpiod_get_optional
Date: Thu, 17 Oct 2019 05:43:24 +0000 [thread overview]
Message-ID: <8de93390-ae04-4278-bb34-aa175c659c23@st.com> (raw)
In-Reply-To: <20191016105604.8036-1-hslester96@gmail.com>
Hello Chuhong,
Is this check necessary ?
since looking into code it seems to me devm_gpiod_get_optional() can only
return NULL in case of error due to following check in devm_gpiod_get_index_optional()
if (IS_ERR(desc)) {
if (PTR_ERR(desc) == -ENOENT)
return NULL;
}
And in that case reset_gpio is not used
Regards
Mickael
On 10/16/19 12:56, Chuhong Yuan wrote:
> mipid02_probe misses a check for devm_gpiod_get_optional and may miss
> the failure.
> Add a check to fix the problem.
>
> Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
> ---
> drivers/media/i2c/st-mipid02.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/media/i2c/st-mipid02.c b/drivers/media/i2c/st-mipid02.c
> index 81285b8d5cfb..d38e888b0a43 100644
> --- a/drivers/media/i2c/st-mipid02.c
> +++ b/drivers/media/i2c/st-mipid02.c
> @@ -971,6 +971,9 @@ static int mipid02_probe(struct i2c_client *client)
> bridge->reset_gpio = devm_gpiod_get_optional(dev, "reset",
> GPIOD_OUT_HIGH);
>
> + if (IS_ERR(bridge->reset_gpio))
> + return PTR_ERR(bridge->reset_gpio);
> +
> ret = mipid02_get_regulators(bridge);
> if (ret) {
> dev_err(dev, "failed to get regulators %d", ret);
>
next prev parent reply other threads:[~2019-10-17 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 10:56 Chuhong Yuan
2019-10-17 5:43 ` Mickael GUENE [this message]
2019-10-17 7:48 ` Chuhong Yuan
2019-10-17 12:24 ` Mickael GUENE
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=8de93390-ae04-4278-bb34-aa175c659c23@st.com \
--to=mickael.guene@st.com \
--cc=hslester96@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®