From: Rob Herring <robh@kernel.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org,
Michael Trimarchi <michael@amarulasolutions.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Stephan Gerhold <stephan@gerhold.net>,
devicetree@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: input: touchscreen: edt-ft5x06: add report-rate
Date: Thu, 24 Feb 2022 16:27:51 -0600 [thread overview]
Message-ID: <YhgGZylBoxlou9ka@robh.at.kernel.org> (raw)
In-Reply-To: <20220217165559.313366-2-dario.binacchi@amarulasolutions.com>
On Thu, Feb 17, 2022 at 05:55:53PM +0100, Dario Binacchi wrote:
> It allows to change the M06/M12 default scan rate.
>
> Co-developed-by: Michael Trimarchi <michael@amarulasolutions.com>
> Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
>
> (no changes since v1)
>
> .../devicetree/bindings/input/touchscreen/edt-ft5x06.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.yaml b/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.yaml
> index 2e8da7470513..aa8517c6f65b 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.yaml
> +++ b/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.yaml
> @@ -85,6 +85,14 @@ properties:
> minimum: 0
> maximum: 80
>
> + report-rate:
Use property unit suffix: report-rate-hz
This should probably be moved to touchscreen.yaml as it seems common.
> + description: Allows setting the scan rate.
> + M06 supports range from 3 (30 Hz) to 14 (140 Hz).
You're using 3 or 30 in this case? Should be 30, but it's not clear. I'd
just list the range in Hz and leave the conversion detail to the driver.
> + M12 supports range from 1 (1 Hz) to 255 (255 Hz).
Use '|' if formatting (newline) is significant.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + minimum: 1
> + maximum: 255
> +
> touchscreen-size-x: true
> touchscreen-size-y: true
> touchscreen-fuzz-x: true
> --
> 2.32.0
>
>
next prev parent reply other threads:[~2022-02-24 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 16:55 [PATCH v2 0/6] Input: edt-ft5x06 - Improve configuration Dario Binacchi
2022-02-17 16:55 ` [PATCH v2 1/6] dt-bindings: input: touchscreen: edt-ft5x06: add report-rate Dario Binacchi
2022-02-24 22:27 ` Rob Herring [this message]
2022-03-13 16:32 ` Dario Binacchi
2022-02-17 16:55 ` [PATCH v2 2/6] Input: edt-ft5x06 - get/set M12 report rate by sysfs Dario Binacchi
2022-02-17 16:55 ` [PATCH v2 3/6] Input: edt-ft5x06 - set report rate by dts property Dario Binacchi
2022-02-17 16:55 ` [PATCH v2 4/6] Input: edt-ft5x06 - show model name by sysfs Dario Binacchi
2022-02-17 16:55 ` [PATCH v2 5/6] Input: edt-ft5x06 - show firmware version " Dario Binacchi
2022-02-17 16:55 ` [PATCH v2 6/6] Input: edt-ft5x06 - show crc and header errors " Dario Binacchi
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=YhgGZylBoxlou9ka@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=stephan@gerhold.net \
/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).