public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Underwood <basicmark@yahoo.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	Pavel Machek <pavel@ucw.cz>, Arjan Van de Ven <arjanv@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>
Subject: How do we handle multi-function devices? [was Re: [patch] ucb1x00: touchscreen cleanups]
Date: Mon, 1 Aug 2005 09:02:46 +0100 (BST)	[thread overview]
Message-ID: <20050801080246.76594.qmail@web30301.mail.mud.yahoo.com> (raw)
In-Reply-To: <1122849209.7626.16.camel@localhost.localdomain>


--- Richard Purdie <rpurdie@rpsys.net> wrote:

> On Sun, 2005-07-31 at 23:11 +0100, Mark Underwood
> wrote:
> > As this isn't the only chip of this sort (i.e. a
> > multi-function chip not on the CPU bus) maybe we
> > should store the bus driver in a common place. If
> > needed we could have a very simple bus driver
> > subsystem (this might already be in the kernel, I
> > haven't looked at the bus stuff) in which you
> register
> > a bus driver and client drivers register with the
> bus
> > driver. Just an idea :-).
> 
> This was the idea with the drivers/soc suggestion
> although I think that
> name is perhaps misleading.
> 
> How about drivers/mfd where mfd = Multi Functional
> Devices?

I was thinking of something like driver/bus into which
we might also be able to put the I2C and LL3 buses.
The only problem is that this might leave some parts
of the multi function chip homeless (if they can't
find a home in other subsystems).

> 
> I think it would be acceptable (and in keeping with
> the other drivers
> e.g. pcmcia) to seeing the arch and platform
> specific modules with the
> main driver as long as the naming reflected it (like
> the existing mcp
> and ucb code does) i.e.:
> 
> mcp-core.c
> mcp-sa1100.c
> ucb1x00-code.c
> ucb1x00-assabet.c
> ucb1x00-collie.c

Maybe, I haven't looked at pcmcia but the I2C
subsystem manages to avoid any arch dependent stuff so
couldn't we? I need to do more homework ;-), but
surely we only need a bus driver (IP block specific,
platform and arch independent), a core driver to
register busses and clients, and client drivers.

> 
> If code can be separated out into subsystems, I'm
> not so sure where they
> should go though. The existing policy would suggest
> drivers/input/touchscreen and sound/xxx for these...
> 
> ucb1x00-ts.c
> ucb1x00-audio.c

Yes, any function of a multi function device that can
live in a subsystem should do otherwise imagine the
mess, for example, with a chip that has a USB master
on it.

Mark

> 
> Opinions/Comments?
> 
> Richard
> 
> 



	
	
		
___________________________________________________________ 
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

  parent reply	other threads:[~2005-08-01  8:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  7:46 [patch] ucb1x00: touchscreen cleanups Pavel Machek
2005-07-26  8:04 ` Mark Underwood
2005-07-26  8:07   ` Pavel Machek
2005-07-30  9:22   ` Russell King
2005-07-30 11:33     ` Mark Underwood
2005-07-30 20:28       ` Russell King
2005-07-30 20:46         ` Pavel Machek
2005-07-30 21:03           ` Russell King
2005-07-31 22:11             ` Mark Underwood
2005-07-31 22:33               ` Richard Purdie
2005-07-31 22:49                 ` Pavel Machek
2005-08-01  8:02                 ` Mark Underwood [this message]
2005-07-30  9:17 ` Russell King
2005-07-30  9:23   ` 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=20050801080246.76594.qmail@web30301.mail.mud.yahoo.com \
    --to=basicmark@yahoo.com \
    --cc=arjanv@redhat.com \
    --cc=hch@infradead.org \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=rpurdie@rpsys.net \
    /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