From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Marek Vasut <marek.vasut@gmail.com>,
alsa-devel@alsa-project.org, Eric Miao <eric.y.miao@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] Palm interrupt driven touchscreen driver
Date: Thu, 4 Jun 2009 10:27:28 +0100 [thread overview]
Message-ID: <20090604092727.GE6983@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20090604091329.GI29926@n2100.arm.linux.org.uk>
On Thu, Jun 04, 2009 at 10:13:29AM +0100, Russell King - ARM Linux wrote:
> On Thu, Jun 04, 2009 at 09:54:07AM +0100, Mark Brown wrote:
> > Now we have more widely
> > distributed platforms merged I see no reason to keep the Mainstone code
> > in mainline.
> Why not? So what do those of us with mainstone platforms but not these
> "more widely distributed platforms" use instead?
This isn't a standard fit module for the Mainstone - it's the Mainstone
with the default audio plugin module replaced by a Wolfson plugin module.
If you just have a standard Mainstone you'd need a different accelerated
touch driver for the relevant AC97 controller.
If there are people out there with these setups then obviously the
driver is worth keeping in mainline, but I'm not aware of any active
users.
next prev parent reply other threads:[~2009-06-04 9:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 21:41 [PATCH] Palm interrupt driven touchscreen driver Marek Vasut
2009-06-04 1:35 ` Eric Miao
2009-06-04 7:20 ` Ian Molton
2009-06-04 8:54 ` Mark Brown
2009-06-04 9:09 ` Jaroslav Kysela
2009-06-04 9:37 ` Mark Brown
2009-06-04 9:44 ` Takashi Iwai
2009-06-04 10:38 ` Mark Brown
2009-06-05 9:16 ` Takashi Iwai
2009-06-05 9:30 ` Mark Brown
2009-06-05 10:05 ` Takashi Iwai
2009-06-05 10:20 ` Mark Brown
2009-06-05 10:38 ` Takashi Iwai
2009-06-05 10:42 ` Mark Brown
2009-06-04 9:13 ` Russell King - ARM Linux
2009-06-04 9:27 ` Mark Brown [this message]
2009-06-04 8:14 ` Russell King - ARM Linux
2009-06-04 20:05 ` Marek Vasut
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=20090604092727.GE6983@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux@arm.linux.org.uk \
--cc=marek.vasut@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 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.