All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Vignesh R <vigneshr@ti.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	Jonathan Corbet <corbet@lwn.net>, Johan Hovold <johan@kernel.org>,
	Sylvain Rochet <sylvain.rochet@finsecur.com>,
	Masanari Iida <standby24x7@gmail.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	S Twiss <stwiss.opensource@diasemi.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Moritz Fischer <moritz.fischer@ettus.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Timo Teras <timo.teras@iki.fi>,
	Guido Martinez <guido@vanguardiasur.com.ar>,
	Clifton Barnes <clifton.a.barnes@gmail.com>,
	Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/2] Input: rotary-encoder- Add support for absolute encoder
Date: Fri, 20 May 2016 16:49:06 -0500	[thread overview]
Message-ID: <20160520214906.GA20973@rob-hp-laptop> (raw)
In-Reply-To: <1463648641-6931-2-git-send-email-vigneshr@ti.com>

On Thu, May 19, 2016 at 02:34:00PM +0530, Vignesh R wrote:
> There are rotary-encoders where GPIO lines reflect the actual position
> of the rotary encoder dial. For example, if dial points to 9, then four
> GPIO lines connected to the rotary encoder will read HLLH(1001b = 9).
> Add support for such rotary-encoder.
> The driver relies on rotary-encoder,absolute-encoder DT property to
> detect such encoders.
> Since, GPIO IRQs are not necessary to work with
> such encoders, optional polling mode support is added using
> input_poll_dev skeleton. This is can be used by enabling
> CONFIG_INPUT_GPIO_ROTARY_ENCODER_POLL_MODE_SUPPORT.
> 
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
>  .../devicetree/bindings/input/rotary-encoder.txt   |   4 +
>  Documentation/input/rotary-encoder.txt             |   9 ++
>  drivers/input/misc/Kconfig                         |  11 ++
>  drivers/input/misc/rotary_encoder.c                | 165 ++++++++++++++++-----
>  4 files changed, 155 insertions(+), 34 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/input/rotary-encoder.txt b/Documentation/devicetree/bindings/input/rotary-encoder.txt
> index 6c9f0c8a846c..9c928dbd1500 100644
> --- a/Documentation/devicetree/bindings/input/rotary-encoder.txt
> +++ b/Documentation/devicetree/bindings/input/rotary-encoder.txt
> @@ -12,6 +12,10 @@ Optional properties:
>  - rotary-encoder,relative-axis: register a relative axis rather than an
>    absolute one. Relative axis will only generate +1/-1 events on the input
>    device, hence no steps need to be passed.
> +- rotary-encoder,absolute-encoder: support encoders where GPIO lines
> +  reflect the actual position of the rotary encoder dial. For example,
> +  if dial points to 9, then four GPIO lines read HLLH(1001b = 9).
> +  In this case, rotary-encoder,steps-per-period needed not be defined.

I think this should be done as a new compatible string rather than a 
property. It seems like fundamentally different h/w.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/2] Input: rotary-encoder- Add support for absolute encoder
Date: Fri, 20 May 2016 16:49:06 -0500	[thread overview]
Message-ID: <20160520214906.GA20973@rob-hp-laptop> (raw)
In-Reply-To: <1463648641-6931-2-git-send-email-vigneshr@ti.com>

On Thu, May 19, 2016 at 02:34:00PM +0530, Vignesh R wrote:
> There are rotary-encoders where GPIO lines reflect the actual position
> of the rotary encoder dial. For example, if dial points to 9, then four
> GPIO lines connected to the rotary encoder will read HLLH(1001b = 9).
> Add support for such rotary-encoder.
> The driver relies on rotary-encoder,absolute-encoder DT property to
> detect such encoders.
> Since, GPIO IRQs are not necessary to work with
> such encoders, optional polling mode support is added using
> input_poll_dev skeleton. This is can be used by enabling
> CONFIG_INPUT_GPIO_ROTARY_ENCODER_POLL_MODE_SUPPORT.
> 
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
>  .../devicetree/bindings/input/rotary-encoder.txt   |   4 +
>  Documentation/input/rotary-encoder.txt             |   9 ++
>  drivers/input/misc/Kconfig                         |  11 ++
>  drivers/input/misc/rotary_encoder.c                | 165 ++++++++++++++++-----
>  4 files changed, 155 insertions(+), 34 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/input/rotary-encoder.txt b/Documentation/devicetree/bindings/input/rotary-encoder.txt
> index 6c9f0c8a846c..9c928dbd1500 100644
> --- a/Documentation/devicetree/bindings/input/rotary-encoder.txt
> +++ b/Documentation/devicetree/bindings/input/rotary-encoder.txt
> @@ -12,6 +12,10 @@ Optional properties:
>  - rotary-encoder,relative-axis: register a relative axis rather than an
>    absolute one. Relative axis will only generate +1/-1 events on the input
>    device, hence no steps need to be passed.
> +- rotary-encoder,absolute-encoder: support encoders where GPIO lines
> +  reflect the actual position of the rotary encoder dial. For example,
> +  if dial points to 9, then four GPIO lines read HLLH(1001b = 9).
> +  In this case, rotary-encoder,steps-per-period needed not be defined.

I think this should be done as a new compatible string rather than a 
property. It seems like fundamentally different h/w.

Rob

  parent reply	other threads:[~2016-05-20 21:49 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19  9:03 [RFC PATCH 0/2] AM335x-ICE: Add support for rotary-encoder Vignesh R
2016-05-19  9:03 ` Vignesh R
2016-05-19  9:03 ` Vignesh R
2016-05-19  9:04 ` [RFC PATCH 1/2] Input: rotary-encoder- Add support for absolute encoder Vignesh R
2016-05-19  9:04   ` Vignesh R
2016-05-19  9:04   ` Vignesh R
2016-05-19 11:25   ` Krzysztof Kozlowski
2016-05-19 11:25     ` Krzysztof Kozlowski
2016-05-19 11:44     ` Vignesh R
2016-05-19 11:44       ` Vignesh R
2016-05-19 11:44       ` Vignesh R
2016-05-20 16:34   ` Dmitry Torokhov
2016-05-20 16:34     ` Dmitry Torokhov
2016-05-20 16:34     ` Dmitry Torokhov
2016-05-23  9:18     ` R, Vignesh
2016-05-23  9:18       ` R, Vignesh
2016-05-23  9:18       ` R, Vignesh
2016-05-25  8:44       ` Vignesh R
2016-05-25  8:44         ` Vignesh R
2016-05-25  8:44         ` Vignesh R
2016-06-16 10:47         ` Vignesh R
2016-06-16 10:47           ` Vignesh R
2016-06-16 10:47           ` Vignesh R
2016-07-19 13:04           ` R, Vignesh
2016-07-19 13:04             ` R, Vignesh
2016-07-19 13:04             ` R, Vignesh
2016-05-20 21:49   ` Rob Herring [this message]
2016-05-20 21:49     ` Rob Herring
2016-05-22 10:26   ` Uwe Kleine-König
2016-05-22 10:26     ` Uwe Kleine-König
2016-05-22 10:26     ` Uwe Kleine-König
2016-05-23 11:18     ` R, Vignesh
2016-05-23 11:18       ` R, Vignesh
2016-05-23 11:18       ` R, Vignesh
     [not found]       ` <5742E710.9-l0cyMroinI0@public.gmane.org>
2016-05-23 13:18         ` Uwe Kleine-König
2016-05-23 13:18           ` Uwe Kleine-König
2016-05-23 13:18           ` Uwe Kleine-König
2016-05-24  5:09           ` Vignesh R
2016-05-24  5:09             ` Vignesh R
2016-05-24  5:09             ` Vignesh R
2016-05-24  8:20             ` Uwe Kleine-König
2016-05-24  8:20               ` Uwe Kleine-König
2016-05-24  8:20               ` Uwe Kleine-König
2016-05-25  8:44               ` Vignesh R
2016-05-25  8:44                 ` Vignesh R
2016-05-25  8:44                 ` Vignesh R
2016-05-19  9:04 ` [RFC PATCH 2/2] ARM: dts: am335x-icev2: Add rotary-encoder node Vignesh R
2016-05-19  9:04   ` Vignesh R
2016-05-19  9:04   ` Vignesh R

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=20160520214906.GA20973@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=arnd@arndb.de \
    --cc=clifton.a.barnes@gmail.com \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=geert@linux-m68k.org \
    --cc=guido@vanguardiasur.com.ar \
    --cc=johan@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=moritz.fischer@ettus.com \
    --cc=standby24x7@gmail.com \
    --cc=stwiss.opensource@diasemi.com \
    --cc=sylvain.rochet@finsecur.com \
    --cc=timo.teras@iki.fi \
    --cc=tony@atomide.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.