From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Wenhua Lin <Wenhua.Lin@unisoc.com>
Cc: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Nuno Sá" <nuno.sa@analog.com>, "Arnd Bergmann" <arnd@arndb.de>,
"Samuel Holland" <samuel@sholland.org>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
"Mattijs Korpershoek" <mkorpershoek@baylibre.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Orson Zhai" <orsonzhai@gmail.com>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Chunyan Zhang" <zhang.lyra@gmail.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
"wenhua lin" <wenhua.lin1994@gmail.com>,
"Xiongpeng Wu" <xiongpeng.wu@unisoc.com>
Subject: Re: [PATCH 1/2] devicetree: bindings: Add keypad driver ducumentation
Date: Tue, 8 Aug 2023 10:11:43 +0100 [thread overview]
Message-ID: <20230808101143.00007bb4@Huawei.com> (raw)
In-Reply-To: <20230808072252.3229-1-Wenhua.Lin@unisoc.com>
On Tue, 8 Aug 2023 15:22:52 +0800
Wenhua Lin <Wenhua.Lin@unisoc.com> wrote:
> Add keypad driver ducumentation.
documentation
Though naming convention for dt-bindings patches does not look like
this. Take a look at what has been accepted as bindings recently.
Also you aren't going to get much review of this without cc'ing the
dt list and maintainers.
>
> Signed-off-by: Wenhua Lin <Wenhua.Lin@unisoc.com>
> ---
> .../bindings/input/sprd-keypad.yaml | 76 +++++++++++++++++++
> 1 file changed, 76 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/sprd-keypad.yaml
>
> diff --git a/Documentation/devicetree/bindings/input/sprd-keypad.yaml b/Documentation/devicetree/bindings/input/sprd-keypad.yaml
> new file mode 100644
> index 000000000000..51710e1eb389
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/sprd-keypad.yaml
> @@ -0,0 +1,76 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright 2023 Unisoc Inc.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/input/sprd-keypad.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Device-Tree bindings for GPIO attached keys
Seems rather more specific than that!
> +
> +maintainers:
> + - Orson Zhai <orsonzhai@gmail.com>
> + - Baolin Wang <baolin.wang7@gmail.com>
> + - Chunyan Zhang <zhang.lyra@gmail.com>
> +
> +description: |
> + Keypad controller is used to interface a SoC with a matrix-keypad device.
> + The keypad controller supports multiple row and column lines.
> + A key can be placed at each intersection of a unique row and a unique column.
> + The keypad controller can sense a key-press and key-release and report the
> + event using a interrupt to the cpu.
CPU
> +
> +properties:
> + compatible:
> + const: sprd,sc9860-keypad
Make sure you follow the guidance on test building your binding and example.
See Documentation/devicetree/bindings/writing-bindings.rst and submitting-patches.rst
This has a lot of issues covered by that document.
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + keypad,num-rows:
> + description: Number of row lines connected to the keypad controller.
> +
> + keypad,num-columns:
> + description: Number of column lines connected to the keypad.
> +
> + debounce-interval:
> + description:
> + Debouncing interval time in milliseconds. If not specified defaults to 5.
> + $ref: /schemas/types.yaml#/definitions/uint32
> +
> + default: 5
> +
> + linux,keymap:
> + description: An array of packed 1-cell entries containing the equivalent
> + of row, column and linux key-code. The 32-bit big endian cell is packed.
> +
> +required:
> + - compatible
> + - reg
> + - keypad,num-rows
> + - keypad,num-columns
> + - linux,keymap
> +
> +unevaluatedProperties: false
> +
> +
> +examples:
> + - |
> + keypad@40250000 {
> + compatible = "sprd,sc9860-keypad";
> + reg = <0x40250000 0x1000>;
> + interrupts = <GIC_SPI 36 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&aonapb_gate CLK_KPD_EB>,
> + <&aonapb_gate CLK_KPD_RTC_EB>;
> + clock-names = "enable", "rtc";
> + keypad,num-rows= <3>;
> + keypad,num-columns = <3>;
> + debounce-interval = <5>;
> + linux,keymap = < 0x00000001
> + 0x01000002
> + 0x00020003>;
> + status = "okay";
Status shouldn't be in an example. Formatting wrong.
IF your binding example doesn't build (this won't) then it won't be accepted
by the dt-binding maintainers and their review is needed for it to be
merged.
Jonathan
> + };
> +...
next prev parent reply other threads:[~2023-08-08 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 7:22 [PATCH 1/2] devicetree: bindings: Add keypad driver ducumentation Wenhua Lin
2023-08-08 9:11 ` Jonathan Cameron [this message]
2023-08-08 13:28 ` Andy Shevchenko
2023-08-10 7:41 ` wenhua lin
2023-08-09 18:31 ` Krzysztof Kozlowski
2023-08-10 7:38 ` wenhua lin
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=20230808101143.00007bb4@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Wenhua.Lin@unisoc.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=baolin.wang@linux.alibaba.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mkorpershoek@baylibre.com \
--cc=nuno.sa@analog.com \
--cc=orsonzhai@gmail.com \
--cc=robert.jarzmik@free.fr \
--cc=samuel@sholland.org \
--cc=wenhua.lin1994@gmail.com \
--cc=xiongpeng.wu@unisoc.com \
--cc=zhang.lyra@gmail.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