From: Darren Hart <dvhart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: 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,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH 1/2] ASoC: rt5677: Add ACPI device probing
Date: Tue, 25 Nov 2014 17:48:24 -0800 [thread overview]
Message-ID: <54753168.9010303@linux.intel.com> (raw)
In-Reply-To: <20141125184304.GK7712@sirena.org.uk>
On 11/25/14 10:43, Mark Brown wrote:
> On Tue, Nov 25, 2014 at 10:33:01AM -0800, Darren Hart wrote:
>> On 11/25/14 09:21, Mark Brown wrote:
>
>>> Given the design of _DSD is to share with DT and we already
>>> have device tree bindings for the device we should be using,
>>> it's not clear to me if we want to grind them all through UEFI
>>> and I suspect they'd be unhappy if we tried but pretty much all
>>> audio CODECs are good candidates for use with ACPI given the
>>> new hardware designs Intel have so if we are doing it I ought
>>> to be bouncing everyone to UEFI forum.
>
>> Right, I realized between sending and driving into the office
>> that my statement might be construed this way. I meant *new* _DSD
>> bindings should go through the ACPI/UEFI forum. Where we can
>> reuse DT bindings, we should absolutely do that, agreed. We
>> should still document this and link to the DT binding so it can
>> be referenced and used even when Linux is not the target OS.
>
> Link from where - do we want to talk to the ACPI/UEFI forum and
> figure out some kind of fast track process for them to add an "it's
> already covered by DT, see here" entry to their database for
> example? We also ought to work out how to make sure ACPI IDs are
> registered there as well, should be possible to have something
> simple as part of that.
>
As to registering ACPI IDs, I believe this is the right link:
http://www.uefi.org/PNP_ACPI_Registry
Or did you mean a HID/CID<->DSD mapping?
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2014-11-26 1:48 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
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 [this message]
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=54753168.9010303@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol@google.com \
--cc=bardliao@realtek.com \
--cc=benzh@chromium.org \
--cc=broonie@kernel.org \
--cc=dgreid@chromium.org \
--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).