mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Conor Dooley <conor@kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: utsav.agarwal@analog.com,
	"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 v4 2/2] dt-bindings: input: Update dtbinding for adp5588
Date: Wed, 03 Jul 2024 10:44:51 +0200	[thread overview]
Message-ID: <d4661ddc1d253678fd62be4c7e19eb0cff4174f6.camel@gmail.com> (raw)
In-Reply-To: <20240702-comic-tannery-792d461e0ab7@spud>

On Tue, 2024-07-02 at 16:42 +0100, Conor Dooley wrote:
> On Mon, Jul 01, 2024 at 10:46:09AM -0700, Dmitry Torokhov wrote:
> > On Mon, Jul 01, 2024 at 04:46:12PM +0100, Conor Dooley wrote:
> > > 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?
> > 
> > Yes, I think it should be enough.
> > 
> > > 
> > > 
> > > >    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.
> > 
> > I think it should be possible to use this chip as a GPIO controller but
> > not an interrupt controller, in which case one does not have to wire up
> > the interrupt line from it. However this requires much more elaborate
> > binding description (i.e. no keys and no "interrupt-controller"
> > property).
> 
> Aye. I can totally understand why you might want to make the interrupt
> portion optional - but it seems unrelated to the rest of the changes in
> the patch (use as a keypad without interrupts could be possible, right?)
> and is unexplained.
> 

IMO, it is related as it's the new usecase (of only using the gpios) that
trigger the interrupt not being required anymore. No, I don't think we can use
the keypad without the interrupt line.

I guess (as you suggested before) we should check if one of the rows/columns
property is present and in that case still make 'interrupts' required.

Agree it should be better explained.

- Nuno Sá
> 


  reply	other threads:[~2024-07-03  8:41 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
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á [this message]
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=d4661ddc1d253678fd62be4c7e19eb0cff4174f6.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=arturs.artamonovs@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@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®