public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: "Gurudatt, Sreenidhi B" <sreenidhi.b.gurudatt@intel.com>
Cc: 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 18:35:36 +0200	[thread overview]
Message-ID: <200907211835.36195.arnd@arndb.de> (raw)
In-Reply-To: <98769532B4BB14429434178695419EAE5F45B41A@bgsmsx501.gar.corp.intel.com>

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 <><

  reply	other threads:[~2009-07-21 16:35 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 [this message]
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=200907211835.36195.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