alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	Bastien Nocera <hadess@hadess.net>
Subject: Re: [PATCH] ASoC: tlv320aix31xx: Add ACPI match for Lenovo 100S
Date: Tue, 19 Apr 2016 14:25:33 -0500	[thread overview]
Message-ID: <5716862D.2020309@linux.intel.com> (raw)
In-Reply-To: <20160419184323.GF3217@sirena.org.uk>



On 04/19/2016 01:43 PM, Mark Brown wrote:
> On Tue, Apr 19, 2016 at 12:57:40PM -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.
> It's in the right form at least, dunno if TI actually registered 10TI
> properly or not though.
The PNP ID for TI is TXN
The ACPI ID is TXNW
TI's PCI ID is 0x104C.

so nope, none of the legit vendor IDs match 10TI, which doesn't follow 
the rules... No one seems to care in the BIOS world though, it's 
becoming a lost cause.

  reply	other threads:[~2016-04-19 19:25 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 [this message]
2016-04-19 22:54     ` Bastien Nocera
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=5716862D.2020309@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=hadess@hadess.net \
    --cc=lgirdwood@gmail.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).