[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200907211835.36195.arnd@arndb.de>
Date: Tue, 21 Jul 2009 18:35:36 +0200
From: Arnd Bergmann <arnd@...db.de>
To: "Gurudatt, Sreenidhi B" <sreenidhi.b.gurudatt@...el.com>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alan Cox <alan@...ux.intel.com>
Subject: Re: x86: IPC driver patch for Intel Moorestown platform
On Tuesday 21 July 2009, Gurudatt, Sreenidhi B wrote:
> 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
>
> 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
> PMIC (Power Management Interrupt Controller). It will typically
> get loaded during boot and gets unloaded on shutdown.
> I don't think it should be loaded and unloaded by the user-space apps.
Well, all modules get loaded from user space (modprobe)
by definition, I was not referring to interactive applictions.
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.
Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists