[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1372224988.9179.5.camel@x230>
Date: Wed, 26 Jun 2013 05:36:29 +0000
From: Matthew Garrett <matthew.garrett@...ula.com>
To: Darren Hart <dvhart@...ux.intel.com>
CC: Olof Johansson <olof@...om.net>,
"David S. Miller" <davem@...emloft.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>,
"peter.p.waskiewicz.jr@...el.com" <peter.p.waskiewicz.jr@...el.com>,
"andriy.shevchenko@...ux.intel.com"
<andriy.shevchenko@...ux.intel.com>,
"danders@...cuitco.com" <danders@...cuitco.com>,
"vishal.l.verma@...el.com" <vishal.l.verma@...el.com>,
Grant Likely <grant.likely@...aro.org>,
"Linus Walleij" <linus.walleij@...aro.org>,
Richard Purdie <richard.purdie@...uxfoundation.org>,
"platform-driver-x86@...r.kernel.org"
<platform-driver-x86@...r.kernel.org>
Subject: Re: [PATCH 4/8] minnowboard: Add base platform driver for the
MinnowBoard
On Tue, 2013-06-25 at 22:32 -0700, Darren Hart wrote:
> are all board-specific. They map GPIO to their fixed functions and
> provide an API for board-specific queries (minnowboard.c), they provide
> example uses (minnowboard-gpio and minnowboard-keys) which aid in
> experimentation and the development of new drivers.
>
> Which of these make sense as ACPI devices in your opinion?
Does the firmware contain a corresponding ACPI device with a specific
_HID that defines the programming model? If so, it should have an ACPI
driver. If not, it shouldn't.
--
Matthew Garrett | mjg59@...f.ucam.org
Powered by blists - more mailing lists