From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Silvan Jegen <s.jegen@gmail.com>
Cc: linux-input@vger.kernel.org, Yangtao Li <frank.li@vivo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] Input: tca6416-keypad - switch to using input core's polling features
Date: Tue, 25 Jul 2023 12:50:59 -0700 [thread overview]
Message-ID: <ZMAno7jWmlBZpAO/@google.com> (raw)
In-Reply-To: <2KN6Z0RZYGDKU.2GGSSC8MYU6GX@homearch.localdomain>
On Tue, Jul 25, 2023 at 09:43:12PM +0200, Silvan Jegen wrote:
> Hi
>
> Just one question below.
>
> Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > Instead of rolling custom polling implementation use input core
> > facilities.
> >
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
> > drivers/input/keyboard/tca6416-keypad.c | 46 ++++++++++---------------
> > 1 file changed, 19 insertions(+), 27 deletions(-)
> >
> > diff --git a/drivers/input/keyboard/tca6416-keypad.c b/drivers/input/keyboard/tca6416-keypad.c
> > index ff665319791e..ebc8b9561266 100644
> > --- a/drivers/input/keyboard/tca6416-keypad.c
> > +++ b/drivers/input/keyboard/tca6416-keypad.c
> > @@ -24,6 +24,8 @@
> > #define TCA6416_INVERT 2
> > #define TCA6416_DIRECTION 3
> >
> > +#define TCA6416_POLL_INTERVAL 100 /* msec */
> > +
> > static const struct i2c_device_id tca6416_id[] = {
> > { "tca6416-keys", 16, },
> > { "tca6408-keys", 8, },
> > @@ -43,7 +45,6 @@ struct tca6416_keypad_chip {
> >
> > struct i2c_client *client;
> > struct input_dev *input;
> > - struct delayed_work dwork;
> > int io_size;
> > int irqnum;
> > u16 pinmask;
> > @@ -85,9 +86,9 @@ static int tca6416_read_reg(struct tca6416_keypad_chip *chip, int reg, u16 *val)
> > return 0;
> > }
> >
> > -static void tca6416_keys_scan(struct tca6416_keypad_chip *chip)
> > +static void tca6416_keys_scan(struct input_dev *input)
> > {
> > - struct input_dev *input = chip->input;
> > + struct tca6416_keypad_chip *chip = input_get_drvdata(input);
> > u16 reg_val, val;
> > int error, i, pin_index;
> >
> > @@ -122,33 +123,20 @@ static void tca6416_keys_scan(struct tca6416_keypad_chip *chip)
> > */
> > static irqreturn_t tca6416_keys_isr(int irq, void *dev_id)
> > {
> > - struct tca6416_keypad_chip *chip = dev_id;
> > -
> > - tca6416_keys_scan(chip);
> > + tca6416_keys_scan(dev_id);
> >
> > return IRQ_HANDLED;
> > }
> >
> > -static void tca6416_keys_work_func(struct work_struct *work)
> > -{
> > - struct tca6416_keypad_chip *chip =
> > - container_of(work, struct tca6416_keypad_chip, dwork.work);
> > -
> > - tca6416_keys_scan(chip);
> > - schedule_delayed_work(&chip->dwork, msecs_to_jiffies(100));
> > -}
> > -
> > static int tca6416_keys_open(struct input_dev *dev)
> > {
> > struct tca6416_keypad_chip *chip = input_get_drvdata(dev);
> >
> > - /* Get initial device state in case it has switches */
> > - tca6416_keys_scan(chip);
> > -
> > - if (chip->use_polling)
> > - schedule_delayed_work(&chip->dwork, msecs_to_jiffies(100));
> > - else
> > + if (!chip->use_polling) {
> > + /* Get initial device state in case it has switches */
> > + tca6416_keys_scan(dev);
> > enable_irq(chip->client->irq);
> > + }
> >
> > return 0;
> > }
> > @@ -157,9 +145,7 @@ static void tca6416_keys_close(struct input_dev *dev)
> > {
> > struct tca6416_keypad_chip *chip = input_get_drvdata(dev);
> >
> > - if (chip->use_polling)
> > - cancel_delayed_work_sync(&chip->dwork);
> > - else
> > + if (!chip->use_polling)
> > disable_irq(chip->client->irq);
> > }
> >
> > @@ -232,8 +218,6 @@ static int tca6416_keypad_probe(struct i2c_client *client)
> > chip->pinmask = pdata->pinmask;
> > chip->use_polling = pdata->use_polling;
> >
> > - INIT_DELAYED_WORK(&chip->dwork, tca6416_keys_work_func);
> > -
> > input->phys = "tca6416-keys/input0";
> > input->name = client->name;
> >
> > @@ -268,12 +252,20 @@ static int tca6416_keypad_probe(struct i2c_client *client)
> > return error;
> >
> > if (!chip->use_polling) {
>
> Sorry for my ignorant question but it seems counterituitive that we set
> up polling when chip->use_polling is false. Is this intended?
Nope, this is my brain fart. Thanks for noticing! I'll fix up the
condition before committing...
Thanks.
--
Dmitry
prev parent reply other threads:[~2023-07-25 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 5:30 [PATCH 1/5] Input: tca6416-keypad - always expect proper IRQ number in i2c client Dmitry Torokhov
2023-07-24 5:30 ` [PATCH 2/5] Input: tca6416-keypad - rely on I2C core to set up suspend/resume Dmitry Torokhov
2023-07-24 5:30 ` [PATCH 3/5] Input: tca6416-keypad - fix interrupt enable disbalance Dmitry Torokhov
2023-07-24 5:30 ` [PATCH 4/5] Input: tca6416-keypad - convert to use devm_* api Dmitry Torokhov
2023-07-24 5:30 ` [PATCH 5/5] Input: tca6416-keypad - switch to using input core's polling features Dmitry Torokhov
2023-07-25 19:43 ` Silvan Jegen
2023-07-25 19:50 ` 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=ZMAno7jWmlBZpAO/@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=frank.li@vivo.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.jegen@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).