From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
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 17:23:45 +0200 [thread overview]
Message-ID: <526E8181.2030208@linux.intel.com> (raw)
In-Reply-To: <20131028150639.GA10936@sirena.org.uk>
On 10/28/2013 05:06 PM, Mark Brown wrote:
> On Mon, Oct 28, 2013 at 11:53:14AM +0000, Liam Girdwood wrote:
>> On Fri, 2013-10-25 at 13:42 +0300, Jarkko Nikula wrote:
>>> 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.
> Indeed. The way I initially read the suggestion above the idea was to
> replace the bus number with the ACPI name for the device which seemed
> sensible but now I reread the bus number is still there.
Sorry, my textual proposal above was confusing and should have used
different variables for ACPI name. What I meant was "spix.y" ->
"spi-INTABCD:ij" and "x-00yz" to "i2c-INTABCD:ij" where "INTABCD:ij" was
the ACPI device name which contains the device instance in "ij".
--
Jarkko
next prev parent reply other threads:[~2013-10-28 15:23 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 ` [alsa-devel] " Liam Girdwood
2013-10-28 15:06 ` Mark Brown
2013-10-28 15:23 ` Jarkko Nikula [this message]
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=526E8181.2030208@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 \
--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).