devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: dmitry.torokhov@gmail.com, mark.rutland@arm.com,
	voice.shen@atmel.com, raphaelpereira@gmail.com,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	kernel@pengutronix.de
Subject: Re: [PATCH] Input: qt1050 - add Microchip AT42QT1050 support
Date: Mon, 15 Oct 2018 11:20:29 -0500	[thread overview]
Message-ID: <20181015162029.GA6949@bogus> (raw)
In-Reply-To: <20180924151330.6114-1-m.felsch@pengutronix.de>

On Mon, Sep 24, 2018 at 05:13:30PM +0200, Marco Felsch wrote:
> Add initial support for the AT42QT1050 (QT1050) device. The device
> supports up to five input keys, dependent on the mode. Since it adds only
> the initial support the "1 to 4 keys plus Guard Channel" mode isn't
> support.
> 
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
>  .../bindings/input/microchip,qt1050.txt       |  54 ++

Please split binding patches.

>  drivers/input/keyboard/Kconfig                |  11 +
>  drivers/input/keyboard/Makefile               |   1 +
>  drivers/input/keyboard/qt1050.c               | 589 ++++++++++++++++++
>  4 files changed, 655 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/input/microchip,qt1050.txt
>  create mode 100644 drivers/input/keyboard/qt1050.c
> 
> diff --git a/Documentation/devicetree/bindings/input/microchip,qt1050.txt b/Documentation/devicetree/bindings/input/microchip,qt1050.txt
> new file mode 100644
> index 000000000000..d63e286f6526
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/microchip,qt1050.txt
> @@ -0,0 +1,54 @@
> +Microchip AT42QT1050 Five-channel Touch Sensor IC
> +
> +The AT42QT1050 (QT1050) is a QTouchADC sensor driver. The device can sense from

s/driver/device/

Bindings don't describe drivers.

> +one to five keys, dependent on mode. The QT1050 includes all signal processing
> +functions necessary to provide stable sensing under a wide variety of changing
> +conditions, and the outputs are fully debounced.
> +
> +The touchkey device node should be placed inside an I2C bus node.
> +
> +Required properties:
> +- compatible: Must be "microchip,qt1050"
> +- reg: The I2C address of the touchkeys
> +- interrupts: The sink for the touchpad's IRQ output,
> +  see ../interrupt-controller/interrupts.txt
> +- linux,keycodes: Specifies an array of numeric keycode values to be used for
> +  reporting button presses. The array can contain up to 5 entries. Array index
> +  0 correspond to key 0 and so on. If the keys aren't continuous the
> +  KEY_RESERVED must be used. Keys marked as KEY_RESERVED or not specified will
> +  be disabled.
> +
> +Optional properties:
> +- pre-charge-time: Specifies an array of precharge times in ns for each touch
> +  pad. The value for each pad depend on the hardware layouts. If not specified
> +  or invalid values are specified the default value is taken.
> +  Valid value range [ns]: 0 - 637500; values must be a multiple of 2500;
> +  default is 0.

Needs a unit suffix as defined in property-units.txt.

> +- touchscreen-average-samples: Please see ../input/touchscreen/touchscreen.txt
> +  for more information. Unlike the general binding, this is an array to specify
> +  the samples for each pad. If not specified or invalid values are specified
> +  the default value is taken.
> +  Valid values: 1, 4, 16, 64, 256, 1024, 4096, 16384; default is 1.
> +- touchscreen-pre-scaling: Please see ../input/touchscreen/touchscreen.txt for
> +  more information. Unlike the general binding, this is an array to specify the
> +  scaling factor for each pad. If not specified or invalid values are specified
> +  the default value is taken.
> +  Valid values: 1, 2, 4, 8, 16, 32, 64, 128; default is 1.
> +- touchscreen-fuzz-pressure: Please see ../input/touchscreen/touchscreen.txt for
> +  more information. Unlike the general binding, this is an array to specify the
> +  noise (threshold) value for each pad. If not specified or invalid values are
> +  specified the default value is taken.
> +  Valid value range: 0 - 255; default is 20.
> +
> +Example:
> +QT1050 with 3 non continuous key, key3 and key5 are disabled.
> +
> +touchkeys@41 {
> +	compatible = "microchip,qt1050";
> +	reg = <0x41>;
> +	interrupt-parent = <&gpio0>;
> +	interrupts = <17 IRQ_TYPE_EDGE_FALLING>;
> +	linux,keycodes = <KEY_UP>, <KEY_RIGHT>, <KEY_RESERVED>, <KEY_DOWN>;
> +	touchscreen-average-samples = <64>, <64>, <64>, <256>;
> +	touchscreen-pre-scaling = <16>, <8>, <16>, <16>;
> +};

  reply	other threads:[~2018-10-15 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 15:13 [PATCH] Input: qt1050 - add Microchip AT42QT1050 support Marco Felsch
2018-10-15 16:20 ` Rob Herring [this message]
2018-10-17 22:48   ` Marco Felsch
2018-10-16  3:44 ` Dmitry Torokhov
2018-10-17 23:31   ` Marco Felsch
2018-10-18  0:39     ` Dmitry Torokhov
2018-10-18  8:13       ` Marco Felsch
2018-10-18 18:23         ` Dmitry Torokhov
2018-10-18 21:16           ` Marco Felsch

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=20181015162029.GA6949@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-input@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=mark.rutland@arm.com \
    --cc=raphaelpereira@gmail.com \
    --cc=voice.shen@atmel.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).