From: Conor Dooley <conor@kernel.org>
To: utsav.agarwal@analog.com
Cc: "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>,
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 v4 2/2] dt-bindings: input: Update dtbinding for adp5588
Date: Mon, 1 Jul 2024 16:46:12 +0100 [thread overview]
Message-ID: <20240701-battalion-tacky-c52566b37a97@spud> (raw)
In-Reply-To: <20240701-adp5588_gpio_support-v4-2-44bba0445e90@analog.com>
[-- Attachment #1: Type: text/plain, Size: 2683 bytes --]
On Mon, Jul 01, 2024 at 04:04:51PM +0100, Utsav Agarwal via B4 Relay wrote:
> From: Utsav Agarwal <utsav.agarwal@analog.com>
>
> Updating dt bindings for adp5588. Following properties are now made
> optional:
> - interrupts
> - keypad,num-rows
> - keypad,num-columns
> - linux,keymap
> The proposed new property "gpio-only" has been added as an optional
> property with an additional example.
I can see that as it is clear in the diff, but this doesn't explain why,
which is what you need to do in your commit message.
>
> Signed-off-by: Utsav Agarwal <utsav.agarwal@analog.com>
> ---
> .../devicetree/bindings/input/adi,adp5588.yaml | 28 ++++++++++++++++++----
> 1 file changed, 24 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/input/adi,adp5588.yaml b/Documentation/devicetree/bindings/input/adi,adp5588.yaml
> index 26ea66834ae2..158fbf02cc16 100644
> --- a/Documentation/devicetree/bindings/input/adi,adp5588.yaml
> +++ b/Documentation/devicetree/bindings/input/adi,adp5588.yaml
> @@ -46,6 +46,11 @@ properties:
> '#gpio-cells':
> const: 2
>
> + gpio-only:
> + description:
> + This property applies if keypad,num-rows, keypad,num-columns and
> + linux,keypad are not specified. All keys will be marked as gpio.
Why is a property required for this? Is the absence of the 3 keypad
properties not sufficient to determine that you're in this mode?
> interrupt-controller:
> description:
> This property applies if either keypad,num-rows lower than 8 or
> @@ -68,10 +73,6 @@ properties:
> required:
> - compatible
> - reg
> - - interrupts
I don't understand why interrupts is no longer required.
> - - keypad,num-rows
> - - keypad,num-columns
> - - linux,keymap
I think you should configure "dependencies:" such that if one of these
properties is added, then all 3 of them must be to preserve the current
requirements while the device is being used in keypad mode.
Thanks,
Conor.
>
> unevaluatedProperties: false
>
> @@ -108,4 +109,23 @@ examples:
> >;
> };
> };
> +
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/input/input.h>
> + #include <dt-bindings/gpio/gpio.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + gpio@34 {
> + compatible = "adi,adp5588";
> + reg = <0x34>;
> +
> + #gpio-cells = <2>;
> + gpio-controller;
> + gpio-only;
> + };
> + };
> +
> ...
>
> --
> 2.34.1
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-01 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 15:04 [PATCH v4 0/2] adp5588-keys: Support for dedicated gpio operation Utsav Agarwal via B4 Relay
2024-07-01 15:04 ` [PATCH v4 1/2] Input: adp5588-keys - add support for pure gpio Utsav Agarwal via B4 Relay
2024-07-01 15:04 ` [PATCH v4 2/2] dt-bindings: input: Update dtbinding for adp5588 Utsav Agarwal via B4 Relay
2024-07-01 15:46 ` Conor Dooley [this message]
2024-07-01 17:46 ` Dmitry Torokhov
2024-07-02 10:20 ` Agarwal, Utsav
2024-07-02 15:42 ` Conor Dooley
2024-07-03 8:44 ` Nuno Sá
2024-07-01 16:27 ` Rob Herring (Arm)
2024-07-02 9:57 ` Agarwal, Utsav
2024-07-01 20:14 ` kernel test robot
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=20240701-battalion-tacky-c52566b37a97@spud \
--to=conor@kernel.org \
--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
all inboxes | Powered by JetHome®