From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Gergo Koteles <soyer@irl.hu>,
Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] ALSA: hda/tas2563: Add tas2563 HDA driver
Date: Thu, 7 Dec 2023 15:00:19 +0200 [thread overview]
Message-ID: <ZXHB4651b8OUAtt8@smile.fi.intel.com> (raw)
In-Reply-To: <4cd78962-027c-4bbb-a42a-6ccbca81ac8e@linux.intel.com>
On Wed, Dec 06, 2023 at 05:07:16PM +0100, Amadeusz Sławiński wrote:
> On 12/5/2023 6:22 PM, Pierre-Louis Bossart wrote:
...
> > > > > > > + tas2xxx_generic_fixup(cdc, action, "i2c", "INT8866");
> > > > > >
> > > > > > Any specific reason to use an Intel ACPI identifier? Why not use
> > > > > > "TIAS2563" ?
>
> Will just note that prefix should probably be TXNW (not TIAS) as discussed
> recently on list.
...which should come directly from TI as it's their responsibility to allocate
an ACPI ID.
...
> > > > > INT8866 is in the ACPI.
> > > > > I don't know why Lenovo uses this name.
> > > > > I think it's more internal than intel.
This is wrong (PNP) ID.
...
> > > > > Name (_HID, "INT8866") // _HID: Hardware ID
> > > >
> > > > Ouch, I hope they checked with Intel that this isn't an HID already in
> > > > use...
> > > >
> > > It looks the INT prefix is not reserved. (yet)
> > > https://uefi.org/ACPI_ID_List?acpi_search=INT
You are looking into wrong registry, and yeah, Intel used wrong PNP ID
for years...
> > It's been de-facto reclaimed by Intel over the years, apparently using
> > INTC or INTL was too hard for some of my colleagues...
>
> Perhaps it should be reserved then, so it is present on above list?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-12-07 13:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 23:45 [PATCH 0/2] ALSA: hda/tas2563: Add tas253 HDA driver Gergo Koteles
2023-12-04 23:45 ` [PATCH 1/2] ASoc: tas2563: DSP Firmware loading support Gergo Koteles
2023-12-05 0:05 ` Pierre-Louis Bossart
2023-12-05 1:11 ` Gergo Koteles
2023-12-04 23:45 ` [PATCH 2/2] ALSA: hda/tas2563: Add tas2563 HDA driver Gergo Koteles
2023-12-05 0:22 ` Pierre-Louis Bossart
2023-12-05 1:31 ` Gergo Koteles
2023-12-05 16:01 ` Pierre-Louis Bossart
2023-12-05 16:12 ` Pierre-Louis Bossart
2023-12-05 16:13 ` Mark Brown
2023-12-05 16:59 ` Gergo Koteles
2023-12-05 17:22 ` Pierre-Louis Bossart
2023-12-06 16:07 ` Amadeusz Sławiński
2023-12-07 13:00 ` Andy Shevchenko [this message]
2023-12-10 2:02 ` kernel test robot
2023-12-07 1:05 ` [PATCH 0/2] ALSA: hda/tas2563: Add tas253 " Gergo Koteles
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=ZXHB4651b8OUAtt8@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
--cc=tiwai@suse.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