Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Joachim Eastwood <manabian@gmail.com>
Cc: Michael Welling <mwelling@emacinc.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-input@vger.kernel.org, "Hiremath,
	Vaibhav" <hvaibhav@ti.com>
Subject: Re: TSC2004 driver
Date: Wed, 6 Aug 2014 14:16:26 -0700	[thread overview]
Message-ID: <20140806211626.GC22889@core.coreip.homeip.net> (raw)
In-Reply-To: <CAGhQ9Vy7AhWkAR3ZMxoWnbZ_zpOPvqcL93fqQ=YkpuULO3MVzQ@mail.gmail.com>

On Wed, Aug 06, 2014 at 10:33:18PM +0200, Joachim Eastwood wrote:
> On 6 August 2014 21:37, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > Hi Michael,
> >
> > On Tue, Aug 05, 2014 at 12:06:40PM -0500, Michael Welling wrote:
> >> The TSC2004 driver has yet to appear in the mainline kernel. We have
> >> been using the driver referenced here as provided by TI:
> >>
> >> https://www.mail-archive.com/linux-omap@vger.kernel.org/msg22018.html
> >>
> >> Are there any plans of supporting this device in the mainline kernel?
> >
> > I still believe that support for TSC2004 should be added 5to tsc2007, they are
> > too much alike to be separate drivers.
> 
> I tried to add tsc2004 support to the tsc2007 driver but I didn't
> really get it to work properly because the tsc2007 interrupt handling
> differs from what tsc2004 needs.

OK.

> 
> I think it would be better to add tsc2004 support to the tsc2005
> driver. They only difference between those two chips is the interface
> (i2c vs spi). If regmap was added to tsc2005 I think it should be easy
> to support tsc2004.

That would also be acceptable.

Thanks.

-- 
Dmitry

  reply	other threads:[~2014-08-06 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 17:06 TSC2004 driver Michael Welling
2014-08-06 19:37 ` Dmitry Torokhov
2014-08-06 20:33   ` Joachim Eastwood
2014-08-06 21:16     ` Dmitry Torokhov [this message]
2014-08-06 22:13       ` Michael Welling
2014-08-06 22:28         ` Sebastian Reichel
2014-08-06 22:42           ` Michael Welling

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=20140806211626.GC22889@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=manabian@gmail.com \
    --cc=mwelling@emacinc.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