From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Bastien Nocera <hadess@hadess.net>,
linux-input@vger.kernel.org, Dmitry Mastykin <mastichi@gmail.com>
Subject: Re: [PATCH v2 01/11] Input: goodix - Refactor IRQ pin GPIO accesses
Date: Fri, 6 Mar 2020 15:58:50 -0800 [thread overview]
Message-ID: <20200306235850.GK217608@dtor-ws> (raw)
In-Reply-To: <63a3f7ca-d2c8-2e42-4934-a7e7ca521507@redhat.com>
On Fri, Mar 06, 2020 at 09:54:26AM +0100, Hans de Goede wrote:
> Hi,
>
> On 3/6/20 5:03 AM, Dmitry Torokhov wrote:
> > Hi Hans,
> >
> > On Thu, Mar 05, 2020 at 11:01:22PM +0100, Hans de Goede wrote:
> > > Suspending Goodix touchscreens requires changing the interrupt pin to
> > > output before sending them a power-down command. Followed by wiggling
> > > the interrupt pin to wake the device up, after which it is put back
> > > in input mode.
> > >
> > > So far we have only effectively supported this on devices which use
> > > devicetree. On X86 ACPI platforms both looking up the pins; and using a
> > > pin as both IRQ and GPIO is a bit more complicated. E.g. on some devices
> > > we cannot directly access the IRQ pin as GPIO and we need to call ACPI
> > > methods to control it instead.
> > >
> > > This commit adds a new irq_pin_access_method field to the goodix_chip_data
> > > struct and adds goodix_irq_direction_output and goodix_irq_direction_input
> > > helpers which together abstract the GPIO accesses to the IRQ pin.
> > >
> > > This is a preparation patch for adding support for properly suspending the
> > > touchscreen on X86 ACPI platforms.
> > >
> > > BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1786317
> > > BugLink: https://github.com/nexus511/gpd-ubuntu-packages/issues/10
> > > BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=199207
> > > Cc: Dmitry Mastykin <mastichi@gmail.com>
> > > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > > ---
> > > Changes in v2:
> > > - Make enum member names upper-case
> > > ---
> > > drivers/input/touchscreen/goodix.c | 62 ++++++++++++++++++++++++------
> > > 1 file changed, 51 insertions(+), 11 deletions(-)
> > >
> > > diff --git a/drivers/input/touchscreen/goodix.c b/drivers/input/touchscreen/goodix.c
> > > index 0403102e807e..9cfbcf3cbca8 100644
> > > --- a/drivers/input/touchscreen/goodix.c
> > > +++ b/drivers/input/touchscreen/goodix.c
> > > @@ -31,6 +31,11 @@
> > > struct goodix_ts_data;
> > > +enum goodix_irq_pin_access_method {
> > > + IRQ_PIN_ACCESS_NONE,
> > > + IRQ_PIN_ACCESS_GPIO,
> > > +};
> > > +
> > > struct goodix_chip_data {
> > > u16 config_addr;
> > > int config_len;
> > > @@ -53,6 +58,7 @@ struct goodix_ts_data {
> > > const char *cfg_name;
> > > struct completion firmware_loading_complete;
> > > unsigned long irq_flags;
> > > + enum goodix_irq_pin_access_method irq_pin_access_method;
> > > unsigned int contact_size;
> > > };
> > > @@ -502,17 +508,48 @@ static int goodix_send_cfg(struct goodix_ts_data *ts,
> > > return 0;
> > > }
> > > +static int goodix_irq_direction_output(struct goodix_ts_data *ts,
> > > + int value)
> > > +{
> > > + switch (ts->irq_pin_access_method) {
> > > + case IRQ_PIN_ACCESS_NONE:
> > > + dev_err(&ts->client->dev,
> > > + "%s called without an irq_pin_access_method set\n",
> > > + __func__);
> > > + return -EINVAL;
> > > + case IRQ_PIN_ACCESS_GPIO:
> > > + return gpiod_direction_output(ts->gpiod_int, value);
> > > + }
> > > +
> > > + return -EINVAL; /* Never reached */
> >
> > I do not like these "never reached" comments. We can either let compiler
> > issue a warning that we did not cover all switch cases, or stick
> > "default:" alongside "case IRQ_PIN_ACCESS_NONE:".
>
> I just tried removing this line, this results in:
>
> CC [M] drivers/input/touchscreen/goodix.o
> drivers/input/touchscreen/goodix.c: In function ‘goodix_irq_direction_output’:
> drivers/input/touchscreen/goodix.c:593:1: warning: control reaches end of non-void function [-Wreturn-type]
> 593 | }
> | ^
Ah, right, we use C, not C++ ;)
>
> And I do not want to add a default label, the switch-case is on an enum type and
> if I do that I loose the useful warnings for one of the enum values not being
> handled in the switch-case.
OK, fair enough.
Thanks.
--
Dmitry
prev parent reply other threads:[~2020-03-06 23:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 22:01 [PATCH v2 01/11] Input: goodix - Refactor IRQ pin GPIO accesses Hans de Goede
2020-03-05 22:01 ` [PATCH v2 02/11] Input: goodix - Make loading the config from disk independent from the GPIO setup Hans de Goede
2020-03-06 4:04 ` Dmitry Torokhov
2020-03-06 9:01 ` Hans de Goede
2020-03-07 0:14 ` Dmitry Torokhov
2020-03-05 22:01 ` [PATCH v2 03/11] Input: goodix - Make resetting the controller at probe " Hans de Goede
2020-03-05 22:01 ` [PATCH v2 04/11] Input: goodix - Add support for getting IRQ + reset GPIOs on Cherry Trail devices Hans de Goede
2020-03-05 22:01 ` [PATCH v2 05/11] Input: goodix - Add support for getting IRQ + reset GPIOs on Bay " Hans de Goede
2020-03-05 22:01 ` [PATCH v2 06/11] Input: goodix - Add support for controlling the IRQ pin through ACPI methods Hans de Goede
2020-03-05 22:01 ` [PATCH v2 07/11] Input: goodix - Move defines to above struct goodix_ts_data declaration Hans de Goede
2020-03-05 22:01 ` [PATCH v2 08/11] Input: goodix - Save a copy of the config from goodix_read_config() Hans de Goede
2020-03-05 22:01 ` [PATCH v2 09/11] Input: goodix - Add minimum firmware size check Hans de Goede
2020-03-05 22:01 ` [PATCH v2 10/11] Input: goodix - Make goodix_send_cfg() take a raw buffer as argument Hans de Goede
2020-03-05 22:01 ` [PATCH v2 11/11] Input: goodix - Restore config on resume if necessary Hans de Goede
2020-03-06 4:03 ` [PATCH v2 01/11] Input: goodix - Refactor IRQ pin GPIO accesses Dmitry Torokhov
2020-03-06 8:54 ` Hans de Goede
2020-03-06 23:58 ` Dmitry Torokhov [this message]
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=20200306235850.GK217608@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=mastichi@gmail.com \
/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).