From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-acpi@vger.kernel.org, alsa-devel@alsa-project.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [alsa-devel] [RFC] ASoC: core: Allow DAI links to be specified by using ACPI names
Date: Mon, 28 Oct 2013 11:53:14 +0000 [thread overview]
Message-ID: <1382961194.2334.23.camel@loki> (raw)
In-Reply-To: <526A4B11.5000802@linux.intel.com>
On Fri, 2013-10-25 at 13:42 +0300, Jarkko Nikula wrote:
> On 10/25/2013 01:06 PM, Mark Brown wrote:
> > OK, I was asking because I was thinking of applying the patch for now;
> > it's not that it's a bad idea it just seems like it's something that
> > might might make sense solved at that level. Equally well I don't know
> > if these systems will work with v3.13 anyway so perhaps it's not so
> > urgent.
> Yes, I don't see any urgent reason to push this hack in. Better to check
> dev_name change first. What I'm going to propose there is "spix.y" to
> "spi-INTABCD:xy" and "x-00yz" to "i2c-INTABCD:xy"
>
We probably need to be able to match on ACPI name alone as some BIOS
settings can change the I2C bus number and break the name match used at
bind time. e.g. on Haswell the codec can either be on I2C bus 0 or 7.
Liam
next prev parent reply other threads:[~2013-10-28 11:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 12:33 [RFC] ASoC: core: Allow DAI links to be specified by using ACPI names Jarkko Nikula
2013-10-03 13:37 ` Mark Brown
2013-10-03 14:22 ` Jarkko Nikula
2013-10-03 15:29 ` [alsa-devel] " Vinod Koul
2013-10-03 16:56 ` Liam Girdwood
2013-10-03 16:19 ` Mark Brown
2013-10-04 6:28 ` Jarkko Nikula
2013-10-04 6:55 ` Rafael J. Wysocki
2013-10-04 7:38 ` Jarkko Nikula
2013-10-04 17:17 ` Rafael J. Wysocki
2013-10-04 6:53 ` Rafael J. Wysocki
2013-10-04 7:22 ` Jarkko Nikula
2013-10-04 17:17 ` Rafael J. Wysocki
2013-10-24 9:51 ` Mark Brown
2013-10-25 6:53 ` Jarkko Nikula
2013-10-25 10:06 ` Mark Brown
2013-10-25 10:42 ` Jarkko Nikula
2013-10-28 11:53 ` Liam Girdwood [this message]
2013-10-28 15:06 ` [alsa-devel] " Mark Brown
2013-10-28 15:23 ` Jarkko Nikula
2013-10-28 16:46 ` 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=1382961194.2334.23.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@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;
as well as URLs for NNTP newsgroup(s).