From: Conor Dooley <conor@kernel.org>
To: "Agarwal, Utsav" <Utsav.Agarwal@analog.com>
Cc: "Hennerich, Michael" <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>,
"Sa, Nuno" <Nuno.Sa@analog.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Artamonovs, Arturs" <Arturs.Artamonovs@analog.com>,
"Bimpikas, Vasileios" <Vasileios.Bimpikas@analog.com>,
"Gaskell, Oliver" <Oliver.Gaskell@analog.com>
Subject: Re: [PATCH v5 3/3] dt-bindings: input: Update dtbinding for adp5588
Date: Wed, 3 Jul 2024 16:57:57 +0100 [thread overview]
Message-ID: <20240703-mandate-hardy-281ddd048b40@spud> (raw)
In-Reply-To: <SJ0PR03MB63432316EE8382033A4396369BDD2@SJ0PR03MB6343.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 4153 bytes --]
On Wed, Jul 03, 2024 at 03:55:11PM +0000, Agarwal, Utsav wrote:
> Hi Conor,
>
> Thank you for your feedback.
> > -----Original Message-----
> > From: Conor Dooley <conor@kernel.org>
> > Sent: Wednesday, July 3, 2024 4:20 PM
> > To: Agarwal, Utsav <Utsav.Agarwal@analog.com>
> > Cc: Hennerich, Michael <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>; Sa,
> > Nuno <Nuno.Sa@analog.com>; linux-input@vger.kernel.org;
> > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; Artamonovs,
> > Arturs <Arturs.Artamonovs@analog.com>; Bimpikas, Vasileios
> > <Vasileios.Bimpikas@analog.com>; Gaskell, Oliver
> > <Oliver.Gaskell@analog.com>
> > Subject: Re: [PATCH v5 3/3] dt-bindings: input: Update dtbinding for adp5588
> >
> > On Wed, Jul 03, 2024 at 11:58:16AM +0100, Utsav Agarwal via B4 Relay
> > wrote:
> > > From: Utsav Agarwal <utsav.agarwal@analog.com>
> > >
> > > Updating dt bindings for adp5588. Since the device can now function in a
> > > purely gpio mode, the following keypad specific properties are now made
> > > optional:
> > > - interrupts
> > > - keypad,num-rows
> > > - keypad,num-columns
> > > - linux,keymap
> > >
> > > However since the above properties are required to be specified when
> > > configuring the device as a keypad, dependencies have been added
> > > such that specifying either one would require the remaining as well.
> > >
> > > Signed-off-by: Utsav Agarwal <utsav.agarwal@analog.com>
> > > ---
> > > .../devicetree/bindings/input/adi,adp5588.yaml | 33
> > ++++++++++++++++++----
> > > 1 file changed, 28 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/input/adi,adp5588.yaml
> > b/Documentation/devicetree/bindings/input/adi,adp5588.yaml
> > > index 26ea66834ae2..6c06464f822b 100644
> > > --- a/Documentation/devicetree/bindings/input/adi,adp5588.yaml
> > > +++ b/Documentation/devicetree/bindings/input/adi,adp5588.yaml
> > > @@ -49,7 +49,10 @@ properties:
> > > interrupt-controller:
> > > description:
> > > This property applies if either keypad,num-rows lower than 8 or
> > > - keypad,num-columns lower than 10.
> > > + keypad,num-columns lower than 10. This property does not apply if
> > > + keypad,num-rows or keypad,num-columns are not specified since the
> > > + device then acts as gpio only, during which interrupts are not
> > > + utilized.
> > >
> > > '#interrupt-cells':
> > > const: 2
> > > @@ -65,13 +68,15 @@ properties:
> > > minItems: 1
> > > maxItems: 2
> > >
> > > +dependencies:
> > > + keypad,num-rows: ["keypad,num-columns"]
> > > + keypad,num-cols: ["keypad,num-rows"]
> > > + linux,keymap: ["keypad,num-rows"]
> >
> > Is what you've got here sufficient? Adding "keypad,num-rows" won't
> > mandate "linux,keymap" which I think is wrong. I think all 3 entries
> > here need to contain both of the other two.
> >
>
> Ah, I can see the issue, thank you for pointing it out - I will be correcting that.
>
> > > + interrupts: ["linux,keymap"]
> >
> > I still don't understand why interrupts are only allowed when the keymap
> > is present. I'd cover the interrupts with something like
> >
> > if:
> > required:
> > - linux,keymap
> > then:
> > required:
> > - interrupts
> >
> > so that interrupts can be used while not in keypad mode. Unless of
> > course there's something (unmentioned in this patch) that prevents that.
>
> In case when the device is not in keypad mode, i.e, is purely using gpio - it doesn't trigger the interrupt.
> Due to this, I had restricted the same to keypad mode only(as a requirement). This was mentioned
> here:
> https://lore.kernel.org/all/d4661ddc1d253678fd62be4c7e19eb0cff4174f6.camel@gmail.com/
This says "not required", not "not functional". How come generating
interrupts becomes impossible when not in keypad mode? That's what needs
to be explained.
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-03 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 10:58 [PATCH v5 0/3] adp5588-keys: Support for dedicated gpio operation Utsav Agarwal via B4 Relay
2024-07-03 10:58 ` [PATCH v5 1/3] iInput: adp5588-keys - use guard notation when acquiring mutexes Utsav Agarwal via B4 Relay
2024-07-03 10:58 ` [PATCH v5 2/3] Input: adp5588-keys - add support for pure gpio Utsav Agarwal via B4 Relay
2024-07-03 10:58 ` [PATCH v5 3/3] dt-bindings: input: Update dtbinding for adp5588 Utsav Agarwal via B4 Relay
2024-07-03 15:20 ` Conor Dooley
2024-07-03 15:55 ` Agarwal, Utsav
2024-07-03 15:57 ` Conor Dooley [this message]
2024-07-04 7:19 ` Nuno Sá
2024-07-04 8:47 ` Agarwal, Utsav
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=20240703-mandate-hardy-281ddd048b40@spud \
--to=conor@kernel.org \
--cc=Arturs.Artamonovs@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=Oliver.Gaskell@analog.com \
--cc=Utsav.Agarwal@analog.com \
--cc=Vasileios.Bimpikas@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=robh@kernel.org \
/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