From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Markus Burri <markus.burri@mt.com>
Cc: Manuel Traut <manuel.traut@mt.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Marek Vasut <marek.vasut@gmail.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 4/7] dt-bindings: input: matrix_keypad - add missing property
Date: Tue, 25 Feb 2025 09:43:21 -0800 [thread overview]
Message-ID: <Z74BOePro-J4hSTD@google.com> (raw)
In-Reply-To: <Z72YZwBuzW2D9q0b@Debian-VM-Markus.debian>
On Tue, Feb 25, 2025 at 11:16:07AM +0100, Markus Burri wrote:
> On Mon, Feb 24, 2025 at 10:46:09PM -0800, Dmitry Torokhov wrote:
> > On Wed, Feb 19, 2025 at 05:42:00PM +0100, Manuel Traut wrote:
> > > On Fri, Jan 10, 2025 at 06:49:03AM +0100, Markus Burri wrote:
> > > > The property is implemented in the driver but not described in dt-bindings.
> > > > Add missing property 'gpio-activelow' to DT schema.
> > > >
> > > > Signed-off-by: Markus Burri <markus.burri@mt.com>
> > >
> > > Reviewed-by: Manuel Traut <manuel.traut@mt.com>
> > >
> > > > ---
> > > > .../devicetree/bindings/input/gpio-matrix-keypad.yaml | 6 ++++++
> > > > 1 file changed, 6 insertions(+)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml b/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> > > > index 0f348b9..9c91224 100644
> > > > --- a/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> > > > +++ b/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> > > > @@ -40,6 +40,12 @@ properties:
> > > > type: boolean
> > > > description: Do not enable autorepeat feature.
> > > >
> > > > + gpio-activelow:
> > > > + type: boolean
> > > > + deprecated: true
> > > > + description:
> > > > + The GPIOs are low active (deprecated).
> > > > + Use the GPIO-flags in gpio controller instead of this property.
> >
> > No, we unfortunately can not rely on GPIO-flags. This is not how driver
> > works: current driver behavior is to force GPIOs as active high if the
> > property is missing and ignore polarity specified in GPIO property.
>
> So you mean this property is still valid?
> Current implementation toggle the GPIO flags to low active if the property and the GPIO flags are different.
> So in case of missing property (false) the settings from GPIO flags will be used.
> In case of gpio-activelow (true) GPIO flags are set to low active.
The driver does:
active_low = device_property_read_bool(&pdev->dev, "gpio-activelow");
...
if (active_low ^ gpiod_is_active_low(keypad->col_gpios[i]))
gpiod_toggle_active_low(keypad->col_gpios[i]);
f the property is present active_low is true. If it is absent active_low
is false. And the code below, if GPIO polarity setting from DT disagree
with active_low value it will flip GPIO polarity.
You probably think that gpiod_toggle_active_low() sets line as active
low, when in fact it flips to opposite setting:
void gpiod_toggle_active_low(struct gpio_desc *desc)
{
VALIDATE_DESC_VOID(desc);
change_bit(FLAG_ACTIVE_LOW, &desc->flags);
^^^ flip, not set or clear.
gpiod_line_state_notify(desc, GPIO_V2_LINE_CHANGED_CONFIG);
}
>
> So I will remove the deprecated flag and change the description to:
> "Force GPIO flags to active low. Use GPIO flags if property is missing."
> OK?
No. It should say:
"Force GPIO polarity to active low. In the absence of this property
GPIOs are treated as active high."
Thanks.
--
Dmitry
next prev parent reply other threads:[~2025-02-25 17:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 5:48 [PATCH v5 0/7] Input: matrix-keypad: Various performance improvements Markus Burri
2025-01-10 5:49 ` [PATCH v5 1/7] Input: matrix_keypad - use fsleep for variable delay duration Markus Burri
2025-02-19 16:34 ` Manuel Traut
2025-02-25 6:40 ` Dmitry Torokhov
2025-02-25 6:55 ` Dmitry Torokhov
2025-02-25 8:46 ` Markus Burri
2025-02-26 0:13 ` Dmitry Torokhov
2025-01-10 5:49 ` [PATCH v5 2/7] Input: matrix_keypad - add function for reading row state Markus Burri
2025-02-19 16:40 ` Manuel Traut
2025-01-10 5:49 ` [PATCH v5 3/7] dt-bindings: input: matrix_keypad - convert to YAML Markus Burri
2025-01-14 19:50 ` Rob Herring (Arm)
2025-02-19 16:41 ` Manuel Traut
2025-02-26 0:13 ` Dmitry Torokhov
2025-01-10 5:49 ` [PATCH v5 4/7] dt-bindings: input: matrix_keypad - add missing property Markus Burri
2025-01-14 19:51 ` Rob Herring (Arm)
2025-02-19 16:42 ` Manuel Traut
2025-02-25 6:46 ` Dmitry Torokhov
2025-02-25 10:16 ` Markus Burri
2025-02-25 17:43 ` Dmitry Torokhov [this message]
2025-02-26 12:14 ` Markus Burri
2025-01-10 5:49 ` [PATCH v5 5/7] dt-bindings: input: matrix_keypad - add settle time after enable all columns Markus Burri
2025-02-19 16:42 ` Manuel Traut
2025-02-26 0:14 ` Dmitry Torokhov
2025-01-10 5:49 ` [PATCH v5 6/7] Input: " Markus Burri
2025-02-19 16:47 ` Manuel Traut
2025-02-26 0:14 ` Dmitry Torokhov
2025-01-10 5:49 ` [PATCH v5 7/7] Input: matrix_keypad - detect change during scan Markus Burri
2025-02-19 16:56 ` Manuel Traut
2025-02-25 6:58 ` Dmitry Torokhov
2025-02-25 8:51 ` Markus Burri
2025-02-25 17:46 ` Dmitry Torokhov
2025-02-26 12:06 ` Markus Burri
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=Z74BOePro-J4hSTD@google.com \
--to=dmitry.torokhov@gmail.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=manuel.traut@mt.com \
--cc=marek.vasut@gmail.com \
--cc=markus.burri@mt.com \
--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;
as well as URLs for NNTP newsgroup(s).