linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@hansjkoch.de>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: linux-kernel <linux-input@vger.kernel.org>,
	"daniel@caiaq.de" <daniel@caiaq.de>,
	"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
	"gregkh@suse.de" <gregkh@suse.de>,
	"hjk@hansjkoch.de" <hjk@hansjkoch.de>
Subject: Re: Driver support for TI's quadrature encoder module
Date: Thu, 8 Sep 2011 17:18:17 +0200	[thread overview]
Message-ID: <20110908151817.GA4064@local> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593025743EEE8@dbde02.ent.ti.com>

On Thu, Sep 08, 2011 at 06:57:04PM +0530, AnilKumar, Chimata wrote:
> Hi All,
> 
> I am developing a driver for TI's enhanced Quadrature Encoder Pulse
> (eQEP) module. Details of the module at
> http://www.ti.com/lit/ug/sprufu8/sprufu8.pdf
> 
> Little description about the module:-
> 
> This module is used for direct interface with a linear or rotary
> incremental encoder.
> 
> Main features of the module:
> a. Provides the direction of the motor (clock or anti-clock)
> b. Provides position count values, which can be used to compute speed
>    of a machine (motor/generator)
> c. Generate a sync output from position compare sub-module
> d. Can be used for High & Low speed measurements
> 
> This module has 4 inputs from external rotary/linear encoder.
> a. Input A (Input from external rotary encoder, a pulse train)
> b. Input B (Input from external rotary encoder, a pulse train)
> c. Index Event (Input from external rotary encoder, a index event.
>    This can be used as output, which can be generated after
>    position compare)
> d. Strobe Event (Input from external rotary encoder, a strobe event.
>    This can be used as output, which can be generated after
>    position compare)
> 
> The module provides pre-analyzed data based on the above four input
> signals. We can use the data directly for knowing the position and
> direction details.
> 
> I have few questions related to this:-
> 
> 1. What subsystem this driver fit into? Input subsystem or UIO
> subsystem?

That depends on which bus your module appears. If it looks like
memory that can be mapped to userspace, then UIO could be the
right subsystem. If it has an i2c, spi, usb or similar interface,
then UIO is not the right choice.

You should also look for similar drivers already in the kernel.
Have a look at the IIO subsystem that is under development in
staging. It was designed for things like that. If there already is
a subsystem that handles similar devices, then it should be
preferred over UIO.

Thanks,
Hans


      parent reply	other threads:[~2011-09-08 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 13:27 Driver support for TI's quadrature encoder module AnilKumar, Chimata
2011-09-08 14:54 ` Greg KH
2011-09-08 16:50   ` Jonathan Cameron
2011-09-09 11:39     ` Jonathan Cameron
2011-09-09 12:05       ` AnilKumar, Chimata
2011-09-09 12:27         ` Jonathan Cameron
2011-09-09 12:33           ` AnilKumar, Chimata
2011-09-08 15:18 ` Hans J. Koch [this message]

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=20110908151817.GA4064@local \
    --to=hjk@hansjkoch.de \
    --cc=anilkumar@ti.com \
    --cc=daniel@caiaq.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-input@vger.kernel.org \
    /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).