From: "andrzej zaborowski" <balrogg@gmail.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OMAP tsc210x touchscreens?
Date: Mon, 29 Oct 2007 18:11:19 +0100 [thread overview]
Message-ID: <fb249edb0710291011m71aba4faw8ff7ea232b173765@mail.gmail.com> (raw)
In-Reply-To: <4726085C.2010009@googlemail.com>
On 29/10/2007, Dirk Behme <dirk.behme@googlemail.com> wrote:
> andrzej zaborowski wrote:
> > Hi,
> >
> > On 29/10/2007, Dirk Behme <dirk.behme@googlemail.com> wrote:
> >
> >>Because of [1] I looked into drivers/input/touchscreen/omap/ts_hx.c
> >>what need to be done there. And, mmh, looks like
> >>
> >>drivers/input/touchscreen/omap
> >>
> >>can/should be completely removed? I couldn't find any Kconfig using
> >>TOUCHSCREEN_OMAP, so touchscreen/omap will never compile?
> >>
> >>Instead, touchscreen/tsc210x_ts.c should be used? tsc2102_ts.c is
> >>outdated and replaced by tsc210x_ts.c now as well?
> >
> >
> > Yes, kindof, the tsc210x* files were supposed to replace tsc2101* and
> > tsc2102* but tsc210x completely doesn't support audio yet,
>
> Anything in touchscreen/* should be completely independent from audio?
The thing is that drivers/input/touchscreen/tsc2102_ts.c is selectable
only if driver/spi/tsc2102.c is enabled, likewise with tsc210x* and
other multi-function chips drivers. So, if you need audio you will
need to select a tsc2102_ts.c (or whatever H2 uses), but hopefully
soon this will change and tsc2102* will be dropped.
> In touchscreen/* tsc210x* should be sufficent then and tsc2102* &
> omap/* in *input/touchscreen* are redundant?
I think it was decided that drivers/input/touchscreen/omap/* was going
to be slowly removed. The code there is very platform dependent, but
it does have an advantage of being very simple and fast as is usual
for platform specific code.
Regards
prev parent reply other threads:[~2007-10-29 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 15:30 OMAP tsc210x touchscreens? Dirk Behme
2007-10-29 16:06 ` andrzej zaborowski
2007-10-29 16:20 ` Dirk Behme
2007-10-29 17:11 ` andrzej zaborowski [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=fb249edb0710291011m71aba4faw8ff7ea232b173765@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.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