From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: utsav.agarwal@analog.com
Cc: "Michael Hennerich" <michael.hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Arturs Artamonovs" <arturs.artamonovs@analog.com>,
"Vasileios Bimpikas" <vasileios.bimpikas@analog.com>,
"Oliver Gaskell" <oliver.gaskell@analog.com>
Subject: Re: [PATCH v8 2/3] Input: adp5588-keys - add support for pure gpio
Date: Fri, 2 Aug 2024 17:37:12 -0700 [thread overview]
Message-ID: <Zq17uABHdNENnwVq@google.com> (raw)
In-Reply-To: <20240704-adp5588_gpio_support-v8-2-208cf5d4c2d6@analog.com>
Hi Utsav,
On Thu, Jul 04, 2024 at 03:26:31PM +0100, Utsav Agarwal via B4 Relay wrote:
> From: Utsav Agarwal <utsav.agarwal@analog.com>
>
> Keypad specific setup is relaxed if no keypad rows/columns are specified,
> enabling a purely gpio operation.
>
> Signed-off-by: Utsav Agarwal <utsav.agarwal@analog.com>
> ---
> drivers/input/keyboard/adp5588-keys.c | 37 +++++++++++++++++++++++++++++++----
> 1 file changed, 33 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/input/keyboard/adp5588-keys.c b/drivers/input/keyboard/adp5588-keys.c
> index 09bcfc6b9408..7c32f8b69a3e 100644
> --- a/drivers/input/keyboard/adp5588-keys.c
> +++ b/drivers/input/keyboard/adp5588-keys.c
> @@ -188,6 +188,7 @@ struct adp5588_kpad {
> u32 cols;
> u32 unlock_keys[2];
> int nkeys_unlock;
> + bool gpio_only;
> unsigned short keycode[ADP5588_KEYMAPSIZE];
> unsigned char gpiomap[ADP5588_MAXGPIO];
> struct gpio_chip gc;
> @@ -431,10 +432,12 @@ static int adp5588_gpio_add(struct adp5588_kpad *kpad)
> kpad->gc.label = kpad->client->name;
> kpad->gc.owner = THIS_MODULE;
>
> - girq = &kpad->gc.irq;
> - gpio_irq_chip_set_chip(girq, &adp5588_irq_chip);
> - girq->handler = handle_bad_irq;
> - girq->threaded = true;
> + if (kpad->client->irq) {
> + girq = &kpad->gc.irq;
> + gpio_irq_chip_set_chip(girq, &adp5588_irq_chip);
> + girq->handler = handle_bad_irq;
> + girq->threaded = true;
> + }
>
> mutex_init(&kpad->gpio_lock);
>
> @@ -632,6 +635,21 @@ static int adp5588_fw_parse(struct adp5588_kpad *kpad)
> struct i2c_client *client = kpad->client;
> int ret, i;
>
> + /*
> + * Check if the device is to be operated purely in GPIO mode. To do
> + * so, check that no keypad rows or columns have been specified,
> + * since all GPINS should be configured as GPIO.
> + */
> + ret = device_property_present(&client->dev,
> + "keypad,num-rows");
> + ret |= device_property_present(&client->dev,
> + "keypad,num-columns");
> + /* If purely GPIO, skip keypad setup */
> + if (!ret) {
> + kpad->gpio_only = true;
> + return 0;
> + }
> +
> ret = matrix_keypad_parse_properties(&client->dev, &kpad->rows,
> &kpad->cols);
> if (ret)
> @@ -775,6 +793,11 @@ static int adp5588_probe(struct i2c_client *client)
> if (error)
> return error;
>
> + if (kpad->gpio_only && !client->irq) {
> + dev_info(&client->dev, "Rev.%d, started as GPIO only\n", revid);
> + return 0;
I think we need more elaborate handling here (and probably more
elaborate binding yaml file): now that you are making interrupt optional
you should check if interrupt-controller functionality of the GPIO
block/gpiochip is requested. If it was, then we should not allow missing
interrupt. If only GPIO controller is needed, without interrupt
capabilities, tnen running without interrupt is fine.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-08-03 0:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 14:26 [PATCH v8 0/3] adp5588-keys: Support for dedicated gpio operation Utsav Agarwal
2024-07-04 14:26 ` Utsav Agarwal via B4 Relay
2024-07-04 14:26 ` [PATCH v8 1/3] Input: adp5588-keys - use guard notation when acquiring mutexes Utsav Agarwal
2024-07-04 14:26 ` Utsav Agarwal via B4 Relay
2024-07-04 14:26 ` [PATCH v8 2/3] Input: adp5588-keys - add support for pure gpio Utsav Agarwal
2024-07-04 14:26 ` Utsav Agarwal via B4 Relay
2024-07-09 6:36 ` Nuno Sá
2024-07-22 15:27 ` Agarwal, Utsav
2024-07-22 15:46 ` Krzysztof Kozlowski
2024-07-23 8:26 ` Agarwal, Utsav
2024-08-03 0:37 ` Dmitry Torokhov [this message]
2024-08-05 6:43 ` Nuno Sá
2024-08-05 18:36 ` Agarwal, Utsav
2024-07-04 14:26 ` [PATCH v8 3/3] dt-bindings: input: Update dtbinding for adp5588 Utsav Agarwal
2024-07-04 14:26 ` Utsav Agarwal via B4 Relay
2024-07-04 16:12 ` Conor Dooley
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=Zq17uABHdNENnwVq@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=arturs.artamonovs@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--cc=oliver.gaskell@analog.com \
--cc=robh@kernel.org \
--cc=utsav.agarwal@analog.com \
--cc=vasileios.bimpikas@analog.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 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.