From: David Brownell <david-b@pacbell.net>
To: "Trilok Soni" <soni.trilok@gmail.com>
Cc: "Kwangwoo Lee" <kwangwoo.lee@gmail.com>,
dmitry.torokhov@gmail.com, linux-kernel@vger.kernel.org,
"linux-omap@vger.kernel.org Mailing List"
<linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Add tsc2007 based touchscreen driver.
Date: Wed, 3 Dec 2008 12:18:35 -0800 [thread overview]
Message-ID: <200812031218.36036.david-b@pacbell.net> (raw)
In-Reply-To: <5d5443650812030321p77c4941cj2202418f0b0d44a2@mail.gmail.com>
On Wednesday 03 December 2008, Trilok Soni wrote:
> Adding linux-omap mailing list. Sometime I am thinking that same chip
> might have interface to be connected on another board/cpu through SPI
> too, so in this case we will have two drivers doing the same thing and
> difference is just a change of the bus interface.
Is this chip an example of that? It's I2C-only, and a quick
scan of TI's touchscreen chip page didn't show a sibling chip
with a logically-identical interface using SPI.
> We should do something v4l2_subdev framework right now going on on
> v4l2 mailing list to abstract the sensor drivers from bus.
I'll disagree. When it's needed, this is easy to do ... bus
glue talking to chip-specific code, and including some kind of
bus-specific register access wrapper. No framework necessary,
just straightforward design for any such drivers.
- Dave
next prev parent reply other threads:[~2008-12-03 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 13:39 [PATCH] Add tsc2007 based touchscreen driver Kwangwoo Lee
2008-12-03 11:21 ` Trilok Soni
2008-12-03 12:01 ` Felipe Balbi
2008-12-04 5:07 ` Kwangwoo Lee
2008-12-04 9:37 ` Felipe Balbi
2008-12-04 9:56 ` David Brownell
2008-12-05 1:09 ` Kwangwoo Lee
2008-12-03 20:18 ` David Brownell [this message]
2008-12-04 4:37 ` Kwangwoo Lee
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=200812031218.36036.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=dmitry.torokhov@gmail.com \
--cc=kwangwoo.lee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=soni.trilok@gmail.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