From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] Input: tsc2007 - convert to GPIO descriptors
Date: Mon, 8 Mar 2021 11:29:06 -0800 [thread overview]
Message-ID: <YEZ7Atrdg7CAEWYA@google.com> (raw)
In-Reply-To: <CAHp75VerojbEjAjtmFqhyrmyhT_WCZxQihgAac80_GAZHyH9LQ@mail.gmail.com>
On Mon, Mar 08, 2021 at 11:10:38AM +0200, Andy Shevchenko wrote:
> On Mon, Mar 8, 2021 at 12:57 AM Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > On Mon, Mar 08, 2021 at 12:05:48AM +0200, Andy Shevchenko wrote:
>
> ...
>
> > > - return !gpio_get_value(ts->gpio);
> > > + return !gpiod_get_value(ts->gpiod);
> >
> > This is not correct. gpio_get_value() is raw polarity vs
> > gpiod_get_value() using logical active/inactive, and tsc2007 GPIO lines
> > are active low. The negation must be dropped after switching to GPIOD
> > API.
>
> Ah, indeed, I missed that, thanks!
>
> ...
>
> > > - ts->gpio = of_get_gpio(np, 0);
> > > - if (gpio_is_valid(ts->gpio))
> > > - ts->get_pendown_state = tsc2007_get_pendown_state_gpio;
> > > - else
> > > - dev_warn(&client->dev,
> > > - "GPIO not specified in DT (of_get_gpio returned %d)\n",
> > > - ts->gpio);
> > > + ts->gpiod = devm_gpiod_get_optional(dev, NULL, GPIOD_IN);
> >
> > GPIO is definitely not optional in DT case, at least in the way the
> > driver written right now.
>
> Can you elaborate this, please? I don't see from the dev_warn() w/o
> any error code returned that it's mandatory.
> In the bindings one may read:
>
> Optional properties:
> - gpios: the interrupt gpio the chip is connected to (trough the penirq pin).
> The penirq pin goes to low when the panel is touched.
> (see GPIO binding[1] for more details).
>
> Nothing suggested it's mandatory. What have I missed?
Ah, indeed, I misread the code and thought we'd abort if there is no
pendown GPIO. I wonder if we should remove the warning since we seem to
support operations without it.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2021-03-08 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 22:05 [PATCH v1 1/2] Input: tsc2007 - convert to GPIO descriptors Andy Shevchenko
2021-03-07 22:05 ` [PATCH v1 2/2] Input: tsc2007 - make use of device properties Andy Shevchenko
2021-03-07 22:57 ` [PATCH v1 1/2] Input: tsc2007 - convert to GPIO descriptors Dmitry Torokhov
2021-03-08 9:10 ` Andy Shevchenko
2021-03-08 19:29 ` Dmitry Torokhov [this message]
2021-03-08 21:04 ` Andy Shevchenko
2021-03-08 21:12 ` Dmitry Torokhov
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=YEZ7Atrdg7CAEWYA@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).