From: Arnd Bergmann <arnd@arndb.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Gurudatt, Sreenidhi B" <sreenidhi.b.gurudatt@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alan Cox <alan@linux.intel.com>
Subject: Re: x86: IPC driver patch for Intel Moorestown platform
Date: Tue, 21 Jul 2009 17:23:36 +0200 [thread overview]
Message-ID: <200907211723.36862.arnd@arndb.de> (raw)
In-Reply-To: <20090721161023.7607ea7f@lxorguk.ukuu.org.uk>
On Tuesday 21 July 2009, Alan Cox wrote:
> > 1. built-in code adds platform-device for mrst_ipc
> > 2. user space auto-loads the mrst_ipc driver
> > 3. mrst_ipc driver creates child devices for each of its attached
> > devices
>
> The devices talking to it already are devices - but they will be input
> devices, watchdogs, etc. They already belong in existing classes.
Remember that devices normally are both in the /sys/class hierarchy
as a class device and in the /sys/devices hierarchy based on their
attachment.
> I also don't believe the mrst ipc is enumerable either. If it was
> enumerable it would make a lot more sense.
It could be done along the same lines as ./drivers/input/serio/i8042.c:
The platform knows when an i8042 chip is present and adds the
serio devices it statically knows about. The serio driver then
adds input class devices for them. You probably wouldn't /have/
to add a new bus_type but could reuse nested platform devices.
Arnd <><
next prev parent reply other threads:[~2009-07-21 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 1:28 x86: IPC driver patch for Intel Moorestown platform Gurudatt, Sreenidhi B
2009-07-21 6:50 ` Andrey Panin
2009-07-21 7:25 ` Andi Kleen
2009-07-21 11:29 ` Christoph Hellwig
2009-07-21 11:24 ` Arnd Bergmann
2009-07-21 12:10 ` Alan Cox
2009-07-21 15:00 ` Arnd Bergmann
2009-07-21 15:10 ` Alan Cox
2009-07-21 15:23 ` Arnd Bergmann [this message]
2009-07-21 16:00 ` Gurudatt, Sreenidhi B
2009-07-21 16:35 ` Arnd Bergmann
2009-07-21 19:04 ` Mark Brown
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=200907211723.36862.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sreenidhi.b.gurudatt@intel.com \
--cc=x86@kernel.org \
/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