From: Mark Brown <broonie@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Darren Hart <dvhart@linux.intel.com>,
Grant Likely <grant.likely@secretlab.ca>,
Ben Zhang <benzh@chromium.org>,
alsa-devel <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Bard Liao <bardliao@realtek.com>,
Oder Chiou <oder_chiou@realtek.com>,
Anatol Pomozov <anatol@google.com>,
Dylan Reid <dgreid@chromium.org>,
flove@realtek.com, Al Stone <al.stone@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ASoC: rt5677: Add ACPI device probing
Date: Tue, 25 Nov 2014 20:27:22 +0000 [thread overview]
Message-ID: <20141125202722.GA25261@sirena.org.uk> (raw)
In-Reply-To: <2580837.YI0IvfXqRR@vostro.rjw.lan>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
On Tue, Nov 25, 2014 at 09:31:27PM +0100, Rafael J. Wysocki wrote:
> On Tuesday, November 25, 2014 11:07:06 AM Darren Hart wrote:
> > This is a current topic with the ACPI working group. We have the
> > following document:
> > http://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf
> This hasn't been discussed a lot at the meetings I attended.
> The bindings management process is being set up within the UEFI Forum, but I'm
> not sure if/how the existing DT bindings documented in the kernel tree are
> going to be covered by it ATM.
Al Stone (CCed) pointed me at the following two documents:
http://www.uefi.org/sites/default/files/resources/web-page-v2.pdf
http://www.uefi.org/sites/default/files/resources/nic-request-v2.pdf
(the first one being the actual process in so far as it exists). The
process appears to be to mail requests in a specific format to the ASWG
chairperson (the address is apparently supposed to be awsg@uefi.org).
It looks like all the properties are expected to end up in one or more
PDF files like the second one.
My initial thought would be to require that we send any DT properties
defined for devices with ACPI identifiers registered there and hope the
volume doesn't DoS them.
A more defined format for DT documentation that we can script into the
ASWG format (or vice versa) might be helpful here, and we should add
notes to the DT documentation if this is how we want to proceed.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-11-25 20:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 6:56 [PATCH 1/2] ASoC: rt5677: Add ACPI device probing Ben Zhang
2014-11-15 6:56 ` [PATCH 2/2] ASoC: rt5677: add a platform config option for PDM clock divider Ben Zhang
2014-11-25 12:07 ` [PATCH 1/2] ASoC: rt5677: Add ACPI device probing Mark Brown
2014-11-25 12:11 ` Grant Likely
2014-11-25 14:28 ` [alsa-devel] " Liam Girdwood
2014-11-25 16:01 ` Darren Hart
2014-11-25 18:37 ` Liam Girdwood
2014-11-25 16:00 ` Darren Hart
2014-11-25 17:21 ` Mark Brown
2014-11-25 18:33 ` Darren Hart
2014-11-25 18:43 ` Mark Brown
2014-11-25 19:07 ` Darren Hart
2014-11-25 19:36 ` Mark Brown
2014-11-25 20:32 ` Rafael J. Wysocki
2014-11-25 20:31 ` Rafael J. Wysocki
2014-11-25 20:27 ` Mark Brown [this message]
2014-11-25 21:40 ` Rafael J. Wysocki
2014-11-25 22:15 ` Mark Brown
2014-11-25 22:41 ` Ben Zhang
2014-11-25 22:45 ` Mark Brown
2014-12-04 10:48 ` Grant Likely
2014-12-04 16:46 ` Mark Brown
2014-12-04 21:53 ` Rafael J. Wysocki
2014-11-26 1:48 ` Darren Hart
2014-11-26 11:17 ` Mark Brown
2014-11-26 23:09 ` Rafael J. Wysocki
2014-11-28 16:00 ` Mark Brown
2014-11-28 23:51 ` Rafael J. Wysocki
2014-11-29 11:52 ` Mark Brown
2014-11-29 22:27 ` Rafael J. Wysocki
2014-12-01 17:51 ` Mark Brown
2014-12-01 22:16 ` Rafael J. Wysocki
2014-12-01 22:19 ` Mark Brown
2014-12-01 22:55 ` Rafael J. Wysocki
2014-12-04 11:12 ` Grant Likely
2014-12-04 11:51 ` 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=20141125202722.GA25261@sirena.org.uk \
--to=broonie@kernel.org \
--cc=al.stone@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=anatol@google.com \
--cc=bardliao@realtek.com \
--cc=benzh@chromium.org \
--cc=dgreid@chromium.org \
--cc=dvhart@linux.intel.com \
--cc=flove@realtek.com \
--cc=grant.likely@secretlab.ca \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).