public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Darren Hart <dvhart@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	hpa@zytor.com, linus.walleij@linaro.org, rjw@sisk.pl
Subject: Re: ACPI vs Device Tree - moving forward
Date: Tue, 20 Aug 2013 14:36:57 -0700	[thread overview]
Message-ID: <20130820213657.GA23058@roeck-us.net> (raw)
In-Reply-To: <20130820205712.GA22850@srcf.ucam.org>

On Tue, Aug 20, 2013 at 09:57:13PM +0100, Matthew Garrett wrote:
> On Tue, Aug 20, 2013 at 01:51:03PM -0700, Darren Hart wrote:
> 
> > It seems to me that the only way to end up in a situation where the data
> > is reused by other OSes, is to go through a standards body. What about
> > attempting to standardize the _DSM method? I suppose the challenge then
> > is how do we standardize arbitrary data (which, of course, is an
> > oxymoron)...
> 
> Right. We could certainly spec the DT bindings that currently exist, but 
> the obvious pushback is that large chunks of it *are* already in ACPI - 
> a _PS0 method (which is ACPI for "Power up the device") that toggles a 
> GPIO pin, and then provides a different GPIO pin in the DT data, which 
> would we believe?
> 
> > The interesting thing about this to me is that many of these devices are
> > added after-the-fact (as add-on boards, for example). With the
> > MinnowBoard we are looking to provide this configuration data in an
> > EEPROM. Would it make sense for the device manufacturer (rather than the
> > base-board manufacturer) to define the key-value pairs for their
> > hardware?
> 
> Yes, hardware information that's on add-in boards should probably be 
> provided by the add-in board if it carries a ROM. This is trivial on 
> UEFI systems - you just need a UEFI driver for the board that can 
> construct an appropriate SSDT. It's more of a problem for non-UEFI ACPI 
> systems.
> 
> > Sadly, I will not be in New Orleans and am unlikely to receive a Kernel
> > Summit invite, but I am planning be in Edinburgh and would like the
> > opportunity to participate in this discussion.
> 
> I'm not planning on being at kernel summit this year, so I think we'll 
> try to arrange something around that time but outside the event.
> 
For my part I'll be in New Orleans but not in Edinburgh. Meeting in Edinburgh
for the DT/ACPI discussion would of course be an incentive to be there even
without KS invitation, but it is too far to travel just for that purpose.

Guenter

  parent reply	other threads:[~2013-08-20 21:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 19:26 ACPI vs Device Tree - moving forward Matthew Garrett
2013-08-20 20:51 ` Darren Hart
2013-08-20 20:57   ` Matthew Garrett
2013-08-20 21:03     ` Darren Hart
2013-08-20 21:13     ` Rafael J. Wysocki
2013-08-20 21:36     ` Guenter Roeck [this message]
2013-08-20 21:11 ` Rafael J. Wysocki
2013-08-20 23:29   ` Rafael J. Wysocki
2013-08-21 15:57   ` Linus Walleij
2013-08-21 16:09     ` Matthew Garrett
2013-08-21 23:11       ` Rafael J. Wysocki
2013-08-21 23:39         ` Matthew Garrett
2013-08-22  0:02           ` Rafael J. Wysocki
2013-08-22  0:03             ` Matthew Garrett
2013-08-23 23:25               ` Darren Hart
2013-08-23 23:38                 ` Matthew Garrett
2013-08-23 23:45                   ` Darren Hart
2013-08-24  0:13                     ` Guenter Roeck
2013-08-24  1:10                       ` Matthew Garrett
2013-08-24  1:47                         ` Guenter Roeck
2013-08-24  2:38                           ` Matthew Garrett
2013-08-24  2:55                             ` Guenter Roeck
2013-08-24  3:06                               ` Matthew Garrett
2013-08-24  4:45                                 ` Guenter Roeck
2013-08-24  4:51                                   ` Matthew Garrett
2013-08-24  5:30                                     ` Guenter Roeck
2013-08-26  9:32                       ` Linus Walleij
2013-08-26 10:48                         ` Graeme Gregory

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=20130820213657.GA23058@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dvhart@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    /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