From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: broonie@kernel.org, tiwai@suse.com, perex@perex.cz,
amadeuszx.slawinski@linux.intel.com, flove@realtek.com,
oder_chiou@realtek.com, shumingf@realtek.com,
linux-sound@vger.kernel.org
Subject: Re: [PATCH v2 00/22] ASoC: codecs: Update device_id tables for Realtek drivers
Date: Wed, 26 Feb 2025 16:06:31 +0200 [thread overview]
Message-ID: <Z78f5wn0kqJTn4Bh@smile.fi.intel.com> (raw)
In-Reply-To: <20250226112612.166989-1-cezary.rojewski@intel.com>
On Wed, Feb 26, 2025 at 12:25:50PM +0100, Cezary Rojewski wrote:
> The series aims to streamline the formatting for ACPI IDs so that a
> single pattern can be used to identify the device.
>
> Work implicitly suggested by Andy Shevchenko - reading and learning from
> number of his reviews on the Linux mailing lists.
>
> Several formats do exists, however, after technical discussion PCI-based
> format has been selected as the recommended one. For Realtek devices, it
> is going to be 10ECxxxx where 10EC unambiguously identifies Realtek
> company whereas the following 4 hexes specify the PART_ID i.e.: the
> device.
>
> While at it, there shall be no comma after the terminator entry and
> initializing fields with 0 for statically defined structs is redundant.
>
> Patches sorted into two groups:
> - fixes, no functional changes
> - updates: fix + addition of new ACPI ID entries
For all
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-02-26 14:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 11:25 [PATCH v2 00/22] ASoC: codecs: Update device_id tables for Realtek drivers Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 01/22] ASoC: codecs: rt1011: Fix definition of device_id tables Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 02/22] ASoC: codecs: rt1015: " Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 03/22] ASoC: codecs: rt1016: " Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 04/22] ASoC: codecs: rt1019: " Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 05/22] ASoC: codecs: rt1305: " Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 06/22] ASoC: codecs: rt1308: " Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 07/22] ASoC: codecs: rt1318: " Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 08/22] ASoC: codecs: rt274: " Cezary Rojewski
2025-02-26 11:25 ` [PATCH v2 09/22] ASoC: codecs: rt5514: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 10/22] ASoC: codecs: rt5640: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 11/22] ASoC: codecs: rt5645: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 12/22] ASoC: codecs: rt5651: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 13/22] ASoC: codecs: rt5659: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 14/22] ASoC: codecs: rt5660: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 15/22] ASoC: codecs: rt5663: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 16/22] ASoC: codecs: rt5665: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 17/22] ASoC: codecs: rt5668: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 18/22] ASoC: codecs: rt5670: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 19/22] ASoC: codecs: rt5682: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 20/22] ASoC: codecs: rt286: Update " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 21/22] ASoC: codecs: rt298: " Cezary Rojewski
2025-02-26 11:26 ` [PATCH v2 22/22] ASoC: codecs: rt5677: " Cezary Rojewski
2025-02-26 14:06 ` Andy Shevchenko
2025-02-26 14:06 ` Andy Shevchenko [this message]
2025-03-04 15:35 ` [PATCH v2 00/22] ASoC: codecs: Update device_id tables for Realtek drivers 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=Z78f5wn0kqJTn4Bh@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=flove@realtek.com \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=shumingf@realtek.com \
--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