From: "Nuno Sá" <noname.nuno@gmail.com>
To: utsav.agarwal@analog.com,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>
Cc: 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: Tue, 09 Jul 2024 08:36:35 +0200 [thread overview]
Message-ID: <9c64adf6a686b2845c15b368592115f3f9ab39e4.camel@gmail.com> (raw)
In-Reply-To: <20240704-adp5588_gpio_support-v8-2-208cf5d4c2d6@analog.com>
On Thu, 2024-07-04 at 15:26 +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>
> ---
Reviewed-by: Nuno Sa <nuno.sa@analog.com>
next prev parent reply other threads:[~2024-07-09 6:32 UTC|newest]
Thread overview: 12+ 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 via B4 Relay
2024-07-04 14:26 ` [PATCH v8 1/3] Input: adp5588-keys - use guard notation when acquiring mutexes Utsav Agarwal via B4 Relay
2024-07-04 14:26 ` [PATCH v8 2/3] Input: adp5588-keys - add support for pure gpio Utsav Agarwal via B4 Relay
2024-07-09 6:36 ` Nuno Sá [this message]
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
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 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=9c64adf6a686b2845c15b368592115f3f9ab39e4.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=arturs.artamonovs@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--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 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).