From: Bastien Nocera <hadess@hadess.net>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: tlv320aix31xx: Add ACPI match for Lenovo 100S
Date: Wed, 20 Apr 2016 00:54:14 +0200 [thread overview]
Message-ID: <1461106454.7279.25.camel@hadess.net> (raw)
In-Reply-To: <57167194.2030803@linux.intel.com>
On Tue, 2016-04-19 at 12:57 -0500, Pierre-Louis Bossart wrote:
>
> On 04/19/2016 11:41 AM, Mark Brown wrote:
> >
> > On Tue, Apr 19, 2016 at 06:00:20PM +0200, Bastien Nocera wrote:
> >
> > >
> > > +static const struct acpi_device_id aic31xx_acpi_match[] = {
> > > + { "10TI3100", 0 },
> > An ACPI identifier that actually bears some resemblance to the name of
> > the part, will wonders never cease! :)
> It's not a legit ACPI id but at least it's consistent with other BIOS. I
> see the same in a couple of DSDT I extracted. it'd be curious to see the
> schematics if you have them to help progress with Baytrail-CR support.
The DSDT for that device is at:
http://noraisin.net/lenovo-100s/dsdt.dsl
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-04-19 22:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 16:00 [PATCH] ASoC: tlv320aix31xx: Add ACPI match for Lenovo 100S Bastien Nocera
2016-04-19 16:41 ` Mark Brown
2016-04-19 17:57 ` Pierre-Louis Bossart
2016-04-19 18:43 ` Mark Brown
2016-04-19 19:25 ` Pierre-Louis Bossart
2016-04-19 22:54 ` Bastien Nocera [this message]
2016-04-19 16:41 ` Applied "ASoC: tlv320aix31xx: Add ACPI match for Lenovo 100S" to the asoc tree Mark Brown
2016-06-01 16:16 ` 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=1461106454.7279.25.camel@hadess.net \
--to=hadess@hadess.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@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).