From: Darren Hart <dvhart@linux.intel.com>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: Olof Johansson <olof@lixom.net>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"peter.p.waskiewicz.jr@intel.com"
<peter.p.waskiewicz.jr@intel.com>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"danders@circuitco.com" <danders@circuitco.com>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>,
Grant Likely <grant.likely@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH 4/8] minnowboard: Add base platform driver for the MinnowBoard
Date: Wed, 26 Jun 2013 00:17:32 -0700 [thread overview]
Message-ID: <1372231052.8177.68.camel@envy.home> (raw)
In-Reply-To: <1372224988.9179.5.camel@x230>
On Wed, 2013-06-26 at 05:36 +0000, Matthew Garrett wrote:
> 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.
It does not currently. However, the firmware is being developed along
with the hardware and the OS. We have the opportunity to do whatever
makes the most sense.
My next-steps here were to get a basic ACPI ID setup for each of the
three drivers just so they could be enumerated over ACPI rather than
just loaded manually. Beyond that I'll be looking to Len and Rafael for
guidance.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-06-26 7:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1372211451.git.dvhart@linux.intel.com>
2013-06-26 1:53 ` [PATCH 4/8] minnowboard: Add base platform driver for the MinnowBoard Darren Hart
2013-06-26 4:00 ` Olof Johansson
2013-06-26 4:43 ` Darren Hart
2013-06-26 4:52 ` Matthew Garrett
2013-06-26 5:32 ` Darren Hart
2013-06-26 5:36 ` Matthew Garrett
2013-06-26 7:17 ` Darren Hart [this message]
2013-06-27 9:14 ` Linus Walleij
2013-06-28 5:43 ` Darren Hart
2013-07-04 16:26 ` Mark Brown
2013-07-20 17:37 ` Linus Walleij
2013-07-21 23:41 ` Mark Brown
2013-10-30 14:18 ` Darren Hart
2013-10-30 21:36 ` Mark Brown
2013-07-22 0:09 ` Grant Likely
2013-07-22 3:27 ` Darren Hart
2013-06-26 1:53 ` [PATCH 5/8] minnowboard-gpio: Export MinnowBoard expansion GPIO Darren Hart
2013-06-26 7:55 ` Andy Shevchenko
2013-06-26 16:21 ` Darren Hart
2013-06-27 8:18 ` Andy Shevchenko
2013-06-28 4:27 ` Darren Hart
2013-06-26 1:53 ` [PATCH 6/8] minnowboard-keys: Bind MinnowBoard buttons to arrow keys Darren Hart
2013-06-26 8:46 ` Andy Shevchenko
2013-06-26 16:28 ` Darren Hart
2013-06-26 17:16 ` Greg Kroah-Hartman
2013-06-26 17:23 ` Darren Hart
2013-06-26 19:57 ` Linus Walleij
2013-06-26 21:23 ` Darren Hart
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=1372231052.8177.68.camel@envy.home \
--to=dvhart@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=danders@circuitco.com \
--cc=davem@davemloft.net \
--cc=grant.likely@linaro.org \
--cc=hpa@zytor.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=olof@lixom.net \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=vishal.l.verma@intel.com \
/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