From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Gurudatt, Sreenidhi B" <sreenidhi.b.gurudatt@intel.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"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 20:04:03 +0100 [thread overview]
Message-ID: <20090721190402.GD28955@sirena.org.uk> (raw)
In-Reply-To: <200907211835.36195.arnd@arndb.de>
On Tue, Jul 21, 2009 at 06:35:36PM +0200, Arnd Bergmann wrote:
> On Tuesday 21 July 2009, Gurudatt, Sreenidhi B wrote:
> > The IPC driver APIs for host drivers communicate with the SCU
> > (System Controller Unit) firmware on the platform. It is used
> > by many Moorestown platform specific drivers such as Audio,
> > Touch Screen, GPIO, Battery, Power Management etc for accessing
> The real difference is whether it can get autoloaded at
> boot time by udev based on the present device nodes, or
> you need to manually put it into /etc/modules.
> If you simply create platform devices at boot time,
> you get both the autoloading and a reasonable representation
> in /sys/devices/platform/mrst_ipc/... for free.
Yeah, this is sounding like the MFD framework might provide a bit of
help here - it essentially boils down to providing some helpers for
doing what you're suggesting here. At present major users of the MFD
framework include the companion chips like the TWL4030 and WM835x which
fulfil the same sort role as described above in more traditional
embedded systems.
prev parent reply other threads:[~2009-07-21 19:04 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
2009-07-21 16:00 ` Gurudatt, Sreenidhi B
2009-07-21 16:35 ` Arnd Bergmann
2009-07-21 19:04 ` Mark Brown [this message]
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=20090721190402.GD28955@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--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