From: Mark Underwood <basicmark@yahoo.com>
To: Richard Purdie <rpurdie@rpsys.net>, Greg KH <gregkh@suse.de>
Cc: Jamey Hicks <jamey.hicks@hp.com>,
Andrey Volkov <avolkov@varma-el.com>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Where is place of arch independed companion chips?
Date: Mon, 8 Aug 2005 22:09:08 +0100 (BST) [thread overview]
Message-ID: <20050808210908.1672.qmail@web30311.mail.mud.yahoo.com> (raw)
In-Reply-To: <1123019379.7782.86.camel@localhost.localdomain>
--- Richard Purdie <rpurdie@rpsys.net> wrote:
> On Mon, 2005-08-01 at 11:13 -0700, Greg KH wrote:
> > > Good question. I was about to submit a patch
> that created
> > > drivers/platform because the toplevel driver for
> MQ11xx is a
> > > platform_device driver. Any thoughts on this?
> >
> > drivers/platform sounds good to me.
>
> In another thread (about the ucb1x00) we came up
> with the idea of
> drivers/mfd (mfd = multi function devices).
>
> The core and platform specific parts would live here
> with suitable clear
> naming and the subsection specific parts that were
> separable would live
> in the appropriate place within the kernel.
>
> Just another idea to add to the mix and removes the
> dilemma of a
> multifunction device with isn't platform based...
This is where my sugguestion on the ucb1x00 comess in
(although it seems to have ot lost as I have had no
reply :-( ). To repeat myself:
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 need to do more homework ;-), but
I think we need a bus driver (I need to see what the
bus subsystem offers) (IP block specific,
platform and arch independent), a core driver to
register busses and clients, and client drivers.
Mark
>
> Richard
>
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-09 4:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 11:52 Where is place of arch independed companion chips? Andrey Volkov
2005-07-31 4:40 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-07-31 12:21 ` Andrey Volkov
2005-08-01 12:29 ` Jamey Hicks
2005-08-01 18:13 ` Greg KH
2005-08-02 21:49 ` Richard Purdie
2005-08-03 9:09 ` Andrey Volkov
2005-08-08 21:09 ` Mark Underwood [this message]
2005-08-03 6:17 ` 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=20050808210908.1672.qmail@web30311.mail.mud.yahoo.com \
--to=basicmark@yahoo.com \
--cc=avolkov@varma-el.com \
--cc=gregkh@suse.de \
--cc=jamey.hicks@hp.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).