alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Grant Likely <grant.likely@secretlab.ca>
Cc: Ben Zhang <benzh@chromium.org>,
	Oder Chiou <oder_chiou@realtek.com>,
	alsa-devel <alsa-devel@alsa-project.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mark Brown <broonie@kernel.org>,
	Anatol Pomozov <anatol@google.com>,
	Bard Liao <bardliao@realtek.com>,
	Dylan Reid <dgreid@chromium.org>,
	flove@realtek.com
Subject: Re: [alsa-devel] [PATCH 1/2] ASoC: rt5677: Add ACPI device probing
Date: Tue, 25 Nov 2014 08:01:14 -0800	[thread overview]
Message-ID: <5474A7CA.3020106@linux.intel.com> (raw)
In-Reply-To: <1416925686.7260.28.camel@loki>



On 11/25/14 06:28, Liam Girdwood wrote:
> On Tue, 2014-11-25 at 12:11 +0000, Grant Likely wrote:
>> On Sat, Nov 15, 2014 at 6:56 AM, Ben Zhang <benzh@chromium.org> wrote:
>>> The rt5677 codec driver looks for ACPI device ID "RT5677CE",
>>> which is specified in coreboot. This patch allows platform
>>> data to be obtained via ACPI
>>>
>>> Signed-off-by: Ben Zhang <benzh@chromium.org>
>>
>> This looks like an ideal time to talk about shared DT and ACPI driver
>> bindings. This driver /already/ has a firmware binding. It is
>> documented in the kernel under
>> Documentation/bindings/sound/rt5677.txt. We now have a standard method
>> for sharing bindings between DT and ACPI in the _DSD method[1].
>> Support for DSD is in linux-next and getting merged into v3.19. This
>> is exactly the case that _DSD should be used for passing additional
>> data to the driver, and it should use the existing binding.
>>
>> [1] http://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf
>>
>> For a long time we've had the rule on DT that new bindings must be
>> documented before we merge a patch. That rule I think has been a good
>> one, even if it is a little chaoitc. I think when it comes to ACPI
>> drivers that we should be requiring the same: Document the binding,
>> either in the kernel as a DT binding, or point to somewhere else that
>> has the binding documented.
>>
>> Also, since this patch is targeted at v3.19 or later, the
>> device-properties API should be used. Don't create something custom.
>>
> 
> My sentiments exactly, there would be little point having bespoke device
> properties for every single device. Btw, we also need to align here with
> Windows too !
> 

The Windows folks definitely know about _DSD (and helped define it), so
this is a good opportunity to work through that process. Liam, do you
have a good contact to start that discussion?


-- 
Darren Hart
Intel Open Source Technology Center

  reply	other threads:[~2014-11-25 16:01 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   ` Liam Girdwood
2014-11-25 16:01     ` Darren Hart [this message]
2014-11-25 18:37       ` [alsa-devel] " 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
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=5474A7CA.3020106@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=liam.r.girdwood@linux.intel.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).