From: Rob Herring <robh@kernel.org>
To: Markus Burri <markus.burri@mt.com>
Cc: linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
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 v3 4/7] dt-bindings: input: matrix_keypad - add missing property
Date: Tue, 7 Jan 2025 13:27:01 -0600 [thread overview]
Message-ID: <20250107192701.GA1329697-robh@kernel.org> (raw)
In-Reply-To: <20250107135659.185293-5-markus.burri@mt.com>
On Tue, Jan 07, 2025 at 02:56:56PM +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>
>
> ---
> .../devicetree/bindings/input/gpio-matrix-keypad.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml b/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> index 75975a1..b10da65 100644
> --- a/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> +++ b/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> @@ -38,6 +38,9 @@ properties:
> type: boolean
> description: Do not enable autorepeat feature.
>
> + gpio-activelow:
> + type: boolean
> + description: The GPIOs are low active.
Ideally this should be defined correctly in the gpio properties. The
problem is that does a 0 flag value mean active high or I forgot to
define it. There's a similar issue in spi-controller.yaml. I *think* the
problem is better here since this is an active low boolean rather than
an active high boolean.
Of the users in the kernel tree, only
arch/arm/boot/dts/ti/omap/am335x-guardian.dts got this right.
So I think we should mark this deprecated and put a note to use GPIO
flags instead.
Rob
next prev parent reply other threads:[~2025-01-07 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 13:56 [PATCH v3 0/7] Input: matrix-keypad: Various performance improvements Markus Burri
2025-01-07 13:56 ` [PATCH v3 1/7] Input: matrix_keypad - use fsleep for variable delay duration Markus Burri
2025-01-07 19:33 ` Thomas Weißschuh
2025-01-07 13:56 ` [PATCH v3 2/7] Input: matrix_keypad - add function for reading row state Markus Burri
2025-01-07 13:56 ` [PATCH v3 3/7] dt-bindings: input: matrix_keypad - convert to YAML Markus Burri
2025-01-07 19:09 ` Rob Herring
2025-01-07 13:56 ` [PATCH v3 4/7] dt-bindings: input: matrix_keypad - add missing property Markus Burri
2025-01-07 19:27 ` Rob Herring [this message]
2025-01-09 6:04 ` Dmitry Torokhov
2025-01-09 7:53 ` EXTERNAL - " Markus Burri
2025-01-08 8:34 ` Krzysztof Kozlowski
2025-01-07 13:56 ` [PATCH v3 5/7] dt-bindings: input: matrix_keypad - add settle time after enable all columns Markus Burri
2025-01-07 19:27 ` Rob Herring (Arm)
2025-01-07 13:56 ` [PATCH v3 6/7] Input: " Markus Burri
2025-01-07 13:56 ` [PATCH v3 7/7] Input: matrix_keypad - detect change during scan 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=20250107192701.GA1329697-robh@kernel.org \
--to=robh@kernel.org \
--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=marek.vasut@gmail.com \
--cc=markus.burri@mt.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).