From: Johan Hovold <johan@kernel.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
Johan Hovold <johan@kernel.org>,
linux-kernel@vger.kernel.org, greybus-dev@lists.linaro.org
Subject: Re: [PATCH v2] staging: greybus: Use gpio_is_valid()
Date: Wed, 2 May 2018 11:57:37 +0200 [thread overview]
Message-ID: <20180502095737.GG2285@localhost> (raw)
In-Reply-To: <2aa263ef-1bbc-69fc-c007-303e59517081@gmail.com>
On Wed, May 02, 2018 at 03:15:05PM +0530, Arvind Yadav wrote:
> On Wednesday 02 May 2018 02:13 PM, Johan Hovold wrote:
> > On Sat, Apr 28, 2018 at 10:05:39AM +0530, Arvind Yadav wrote:
> >> Replace the manual validity checks for the GPIO with the
> >> gpio_is_valid().
> >>
> >> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
> >> ---
> >> chnage in v2 :
> >> Returning invalid gpio as error instead of -ENODEV.
> >>
> >> drivers/staging/greybus/arche-platform.c | 6 +++---
> >> 1 file changed, 3 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/staging/greybus/arche-platform.c b/drivers/staging/greybus/arche-platform.c
> >> index 83254a7..c3a7da5 100644
> >> --- a/drivers/staging/greybus/arche-platform.c
> >> +++ b/drivers/staging/greybus/arche-platform.c
> >> @@ -448,7 +448,7 @@ static int arche_platform_probe(struct platform_device *pdev)
> >> arche_pdata->svc_reset_gpio = of_get_named_gpio(np,
> >> "svc,reset-gpio",
> >> 0);
> >> - if (arche_pdata->svc_reset_gpio < 0) {
> >> + if (!gpio_is_valid(arche_pdata->svc_reset_gpio)) {
> >> dev_err(dev, "failed to get reset-gpio\n");
> >> return arche_pdata->svc_reset_gpio;
> >
> > I'm sorry, but I don't this change is desirable. of_get_named_gpio()
> > returns a valid gpio number or a negative errno, so there's no need to
> > use the legacy gpio_is_valid() helper here.
> >
> > If you grep for of_get_named_gpio() you'll find that some drivers indeed
> > use that helper this way, but they are in a clear minority.
> >
> > And ultimately, we want to move to using gpio descriptors anyway.
>
> We need to check gpio validity. If we are using of_get_named_gpio() or
> not. of_get_name_gpio() will read a device node and fetch the value.
> But it'll not check that gpio is valid or not valid.
No, I believe you're mistaken here. of_get_named_gpio() does not return
an arbitrary gpio number, unlike what you could possibly find in
legacy board files and for which the gpio_is_valid() helper made sense.
Johan
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-05-02 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 4:35 [PATCH v2] staging: greybus: Use gpio_is_valid() Arvind Yadav
2018-04-28 19:58 ` [greybus-dev] " Alex Elder
2018-05-02 5:44 ` Viresh Kumar
2018-05-02 8:43 ` Johan Hovold
2018-05-02 9:45 ` Arvind Yadav
2018-05-02 9:57 ` Johan Hovold [this message]
2018-05-02 10:50 ` Arvind Yadav
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=20180502095737.GG2285@localhost \
--to=johan@kernel.org \
--cc=arvind.yadav.cs@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.