From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: Intel: sst-acpi: Add support for multiple machine drivers per platform
Date: Thu, 20 Feb 2014 09:04:48 +0200 [thread overview]
Message-ID: <5305A910.2000507@linux.intel.com> (raw)
In-Reply-To: <20140219161544.GM2669@sirena.org.uk>
Hi
On 02/19/2014 06:15 PM, Mark Brown wrote:
> On Wed, Feb 19, 2014 at 04:35:58PM +0200, Jarkko Nikula wrote:
>
>> Matching machine driver is found by looking at ACPI ID which would best
>> match with the driver. Typically this would be the ACPI ID of audio codec
>> but is not tied to it.
> You're going to need DMI matching as well, there's going to be quirks of
> some kind. Otherwise this looks fine if an ugly way of doing it,
> assuming Liam is happy.
Yes, I believe so too. Although we don't have yet a machine that has
routed audio differently around the same codec in a same platform but
I'm sure that will happen. Then I think it's a case by case decision
will that be better to handle in the same machine driver or here in the
loader.
Our target is to get as much as possible data from ACPI but meanwhile
there will be machines where only data is basically just the SST and
codec ACPI IDs + DMI or some other unique identifier.
--
Jarkko
next prev parent reply other threads:[~2014-02-20 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 14:35 [PATCH] ASoC: Intel: sst-acpi: Add support for multiple machine drivers per platform Jarkko Nikula
2014-02-19 16:15 ` Mark Brown
2014-02-19 16:34 ` Liam Girdwood
2014-02-20 7:04 ` Jarkko Nikula [this message]
2014-02-20 8:58 ` Mark Brown
2014-02-19 16:42 ` 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=5305A910.2000507@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.intel.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