Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Oder Chiou <oder_chiou@realtek.com>,
	"broonie@kernel.org" <broonie@kernel.org>
Cc: "tiwai@suse.com" <tiwai@suse.com>,
	"perex@perex.cz" <perex@perex.cz>,
	"amadeuszx.slawinski@linux.intel.com"
	<amadeuszx.slawinski@linux.intel.com>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"Flove(HsinFu)" <flove@realtek.com>,
	"andriy.shevchenko@linux.intel.com"
	<andriy.shevchenko@linux.intel.com>,
	"Shuming [范書銘]" <shumingf@realtek.com>,
	"Jack Yu" <jack.yu@realtek.com>,
	"Derek [方德義]" <derek.fang@realtek.com>
Subject: Re: [PATCH 20/24] ASoC: codecs: rt1015p: Update definition of device_id tables
Date: Wed, 26 Feb 2025 10:42:29 +0100	[thread overview]
Message-ID: <fcb19c07-9daf-4fa4-a856-5e8726a98873@intel.com> (raw)
In-Reply-To: <d1fe2ca16a7c4c9c90bdd5a8480ca497@realtek.com>

On 2025-02-21 3:38 AM, Oder Chiou wrote:
>> -----Original Message-----
>> From: Cezary Rojewski <cezary.rojewski@intel.com>
>> Sent: Thursday, February 20, 2025 7:27 PM
>> To: broonie@kernel.org
>> Cc: tiwai@suse.com; perex@perex.cz; amadeuszx.slawinski@linux.intel.com;
>> linux-sound@vger.kernel.org; Oder Chiou <oder_chiou@realtek.com>;
>> Flove(HsinFu) <flove@realtek.com>; andriy.shevchenko@linux.intel.com;
>> Cezary Rojewski <cezary.rojewski@intel.com>
>> Subject: [PATCH 20/24] ASoC: codecs: rt1015p: Update definition of device_id
>> tables
>>
>>
>> External mail : This email originated from outside the organization. Do not
>> reply, click links, or open attachments unless you recognize the sender and
>> know the content is safe.
>>
>>
>>
>> Follow PCI-based format (10ECxxxx) for ACPI IDs by adding relevant
>> entries to the existing table.
>>
>> While at it, there shall be no comma after the terminator entry and
>> initializing fields with 0 for statically defined structs is redundant.
>>
>> Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
>> ---
>>   sound/soc/codecs/rt1015p.c | 8 +++++---
>>   1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/sound/soc/codecs/rt1015p.c b/sound/soc/codecs/rt1015p.c
>> index 44e7fe3c32da..33917438196f 100644
>> --- a/sound/soc/codecs/rt1015p.c
>> +++ b/sound/soc/codecs/rt1015p.c
>> @@ -133,9 +133,11 @@ MODULE_DEVICE_TABLE(of, rt1015p_device_id);
>>
>>   #ifdef CONFIG_ACPI
>>   static const struct acpi_device_id rt1015p_acpi_match[] = {
>> -       { "RTL1015", 0},
>> -       { "RTL1019", 0},
>> -       { },
>> +       { "RTL1015" },
>> +       { "RTL1019" },
>> +       { "10EC1015" },
>> +       { "10EC1019" },
>> +       {}
> 
> There are different settings for RTL1015, RTL1019, 10EC1015, and 10EC1019.
> RTL1015 and RTL1019 are used for powering up and down via the GPIO.
> 10EC1015 and 10EC1019 are used for the I2C-controlled driver.
> Therefore 10EC1015 and 10EC1019 should be removed.

Sorry for the delay in response and thank for you the feedback.

I'm surprised this hasn't come up earlier in the discussion. I'll 
probably cut off problematic patches so that majority can be merged. 
It's important to have some follow up though, on the subject you 
mentioned. Correct me if I'm wrong but from the .c files it seems:

for DT/ARM rt1015 & rt1015p are represented by:
	.compatible = "realtek,rt1015"
	.compatible = "realtek,rt1015p"

for ACPI/x86 rt1015 & rt1015p are represented by:
	"10EC1015"
	"RTL1015"

The first pair is nice and clean, the second is confusing and error 
prone. Do you know where the second pair originated from?

Kind regards,
Czarek

  reply	other threads:[~2025-02-26  9:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 11:26 [PATCH 00/24] ASoC: codecs: Update device_id tables for Realtek drivers Cezary Rojewski
2025-02-20 11:26 ` [PATCH 01/24] ASoC: codecs: rt1011: Fix definition of device_id tables Cezary Rojewski
2025-02-20 11:26 ` [PATCH 02/24] ASoC: codecs: rt1015: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 03/24] ASoC: codecs: rt1016: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 04/24] ASoC: codecs: rt1019: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 05/24] ASoC: codecs: rt1305: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 06/24] ASoC: codecs: rt1308: " Cezary Rojewski
2025-02-20 14:11   ` Andy Shevchenko
2025-02-20 15:37     ` Cezary Rojewski
2025-02-20 11:26 ` [PATCH 07/24] ASoC: codecs: rt1318: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 08/24] ASoC: codecs: rt274: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 09/24] ASoC: codecs: rt5514: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 10/24] ASoC: codecs: rt5640: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 11/24] ASoC: codecs: rt5645: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 12/24] ASoC: codecs: rt5651: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 13/24] ASoC: codecs: rt5659: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 14/24] ASoC: codecs: rt5660: " Cezary Rojewski
2025-02-20 14:13   ` Andy Shevchenko
2025-02-20 15:42     ` Cezary Rojewski
2025-02-20 11:26 ` [PATCH 15/24] ASoC: codecs: rt5663: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 16/24] ASoC: codecs: rt5665: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 17/24] ASoC: codecs: rt5668: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 18/24] ASoC: codecs: rt5670: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 19/24] ASoC: codecs: rt5682: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 20/24] ASoC: codecs: rt1015p: Update " Cezary Rojewski
2025-02-21  2:38   ` Oder Chiou
2025-02-26  9:42     ` Cezary Rojewski [this message]
2025-02-27  5:11       ` Oder Chiou
2025-02-27 12:43         ` Cezary Rojewski
2025-02-20 11:26 ` [PATCH 21/24] ASoC: codecs: rt286: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 22/24] ASoC: codecs: rt298: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 23/24] ASoC: codecs: rt5677: " Cezary Rojewski
2025-02-20 11:26 ` [PATCH 24/24] ASoC: codecs: rt5682s: " Cezary Rojewski
2025-02-21  2:08   ` Shuming [范書銘]
2025-02-26  9:47     ` Cezary Rojewski
2025-02-20 14:09 ` [PATCH 00/24] ASoC: codecs: Update device_id tables for Realtek drivers Andy Shevchenko
2025-02-20 14:15 ` Andy Shevchenko

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=fcb19c07-9daf-4fa4-a856-5e8726a98873@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=derek.fang@realtek.com \
    --cc=flove@realtek.com \
    --cc=jack.yu@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