From: Richard Purdie <rpurdie@rpsys.net>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Pavel Machek <pavel@suse.cz>,
lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>,
vojtech@suse.cz
Subject: Re: [patch 1/2] Touchscreen support for sharp sl-5500
Date: Sun, 24 Jul 2005 18:01:12 +0100 [thread overview]
Message-ID: <1122224472.7585.82.camel@localhost.localdomain> (raw)
In-Reply-To: <20050724174756.A20019@flint.arm.linux.org.uk>
On Sun, 2005-07-24 at 17:47 +0100, Russell King wrote:
> On Fri, Jul 22, 2005 at 08:01:09PM +0200, Pavel Machek wrote:
> > This adds support for reading ADCs (etc), neccessary to operate touch
> > screen on Sharp Zaurus sl-5500.
>
> I would like to know what the diffs are between my version (attached)
> and this version before they get applied.
>
> The only reason my version has not been submitted is because it lives
> in the drivers/misc directory, and mainline kernel folk don't like
> drivers which clutter up that directory. In fact, I had been told
> that drivers/misc should remain completely empty - which makes this
> set of miscellaneous drivers homeless.
I've been wondering about suggesting the creation of a drivers/soc
directory. The idea would be for it to contain "system on chip" type
support code. I use that description loosely to fit any code which needs
to support drivers in multiple driver subsections.
An example use in my Zaurus tree is the TSC2101 which contains a
touchscreen, battery monitoring and sound. Handhelds.org has devices
such as the ASIC2/ASIC3 in the ipaqs (and other handhelds) which cover
many different drivers subsections.
Where practical, the sub drivers such as the touchscreen could be placed
into the specific driver areas such as drivers/input/touchscreen/ but
the core chip specific support would be in drivers/soc and the files
would be connected.
Would that be acceptable in mainline?
Richard
next prev parent reply other threads:[~2005-07-24 17:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 18:01 [patch 1/2] Touchscreen support for sharp sl-5500 Pavel Machek
2005-07-24 16:47 ` Russell King
2005-07-24 17:01 ` Richard Purdie [this message]
2005-07-24 17:07 ` randy_dunlap
2005-07-25 4:56 ` Pavel Machek
2005-07-25 15:16 ` Dmitry Torokhov
2005-07-25 15:50 ` Russell King
2005-07-25 16:02 ` Dmitry Torokhov
2005-07-25 16:13 ` Russell King
2005-07-25 16:47 ` Dmitry Torokhov
2005-07-25 16:57 ` Russell King
2005-07-25 22:07 ` Pavel Machek
2005-07-25 21:39 ` Pavel Machek
2005-07-25 21:36 ` Pavel Machek
2005-07-25 16:04 ` Russell King
2005-07-25 22:06 ` Pavel Machek
2005-07-25 23:03 ` Russell King
2005-07-26 6:28 ` Pavel Machek
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=1122224472.7585.82.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=vojtech@suse.cz \
/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