[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131030213602.GQ2493@sirena.org.uk>
Date: Wed, 30 Oct 2013 14:36:02 -0700
From: Mark Brown <broonie@...nel.org>
To: Darren Hart <dvhart@...ux.intel.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Lee Jones <lee.jones@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>,
"peter.p.waskiewicz.jr" <peter.p.waskiewicz.jr@...el.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
danders <danders@...cuitco.com>,
"vishal.l.verma" <vishal.l.verma@...el.com>,
Matthew Garrett <matthew.garrett@...ula.com>,
Grant Likely <grant.likely@...aro.org>,
Richard Purdie <richard.purdie@...uxfoundation.org>,
platform-driver-x86 <platform-driver-x86@...r.kernel.org>
Subject: Re: [PATCH 4/8] minnowboard: Add base platform driver for the
MinnowBoard
On Wed, Oct 30, 2013 at 02:18:00PM +0000, Darren Hart wrote:
> On Mon, 2013-07-22 at 00:41 +0100, Mark Brown wrote:
> > I'd expect it to be a bus, yes.
> It seems to me the platform bus already provides everything we need. We
> can just make a platform driver, say platform-id-gpio.c which can get
> it's platform data from OF or ACPI (_PRP proposal from kernel summit
> last week for example). Why would a separate bus type need to be
> defined?
For the identifier space. We ought to be able to register handling for
plugin boards separately to notifying the system of their existance in a
similar fashion to how we register drivers for anything else.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists