alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Oder Chiou <oder_chiou@realtek.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	Graeme.Gregory@linaro.org,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	Flove <flove@realtek.com>, Bard Liao <bardliao@realtek.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: rt286: Add API to set supported jack type
Date: Mon, 11 Aug 2014 10:59:45 +0100	[thread overview]
Message-ID: <1407751185.2487.150.camel@loki> (raw)
In-Reply-To: <20140807173136.GN17528@sirena.org.uk>

On Thu, 2014-08-07 at 18:31 +0100, Mark Brown wrote:
> On Thu, Aug 07, 2014 at 01:43:24AM +0000, Bard Liao wrote:
> 
> > > If this is coming from the hardware design I'd expect this to be configured
> > > via platform data or firmware data rather than with an API.
> > > Why do it this way?
> 
> > Actually, this patch is for Intel platform which doesn't support platform data
> > yet. That's why we create an API so they can call the API in machine driver.
> 
> So, this is something that the people wanting to use ACPI in platforms
> with devices like this are going to have to deal with - we need a way of
> getting configuration to devices.  Traditionally small tweaks have been
> done based on DMI information but that's not at all scalable.  I believe
> newer ACPI specs are trying to accomodate this due to the expanding
> range of systems supporting ACPI.  Punting to the machine driver just
> moves the problem around, it doesn't really address it.
> 

Unfortunately this will be needed for some Broadwell based BIOSes since
the timing of the ACPI spec/implementation has meant that some Broadwell
BIOSes will contain the data whilst most others wont atm :( 

> I've CCed in Graeme Gregory who's been writing some guidelines for this
> sort of thing in the context of ARMv8 serviers - the most recent patch
> is:
> 
>    http://thread.gmane.org/gmane.linux.acpi.devel/69757
> 
> The advice there looks good to me - see the "Device Enumeration"
> section.

This is indeed good, just too late for the initial Broadwell BIOSes that
wont have this _DSD field for the codec (it will be hard coded for
Windows anyway).

Liam

  reply	other threads:[~2014-08-11 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  5:52 [PATCH] ASoC: rt286: Add API to set supported jack type bardliao
2014-08-06 20:54 ` Mark Brown
2014-08-07  1:43   ` Bard Liao
2014-08-07 17:31     ` Mark Brown
2014-08-11  9:59       ` Liam Girdwood [this message]
2014-08-11 12:24         ` Mark Brown
2014-08-14  8:29           ` Liam Girdwood
2014-08-14 19:09             ` [alsa-devel] " 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=1407751185.2487.150.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=Graeme.Gregory@linaro.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=flove@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=oder_chiou@realtek.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;
as well as URLs for NNTP newsgroup(s).