The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Richard Fitzgerald <rf@opensource.cirrus.com>, broonie@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH 1/2] ASoC: cs35l56: Add support for CS35L62 for SoundWire
Date: Fri, 17 Jul 2026 22:38:47 +0200	[thread overview]
Message-ID: <df0e5e52-7c34-4d09-9de1-eafe0405c951@linux.dev> (raw)
In-Reply-To: <20260715120135.939280-2-rf@opensource.cirrus.com>


> diff --git a/sound/soc/codecs/cs35l56-sdw.c b/sound/soc/codecs/cs35l56-sdw.c
> index 0a55b93b96f96..1e442f43b306b 100644
> --- a/sound/soc/codecs/cs35l56-sdw.c
> +++ b/sound/soc/codecs/cs35l56-sdw.c
> @@ -457,6 +457,7 @@ static int cs35l56_sdw_probe(struct sdw_slave *peripheral, const struct sdw_devi
>  		regmap_config = &cs35l56_regmap_sdw;
>  		break;
>  	case 0x3563:
> +	case 0x3562:

nit-pick: is there any reason why 62 is after 63 instead of a regular
increasing order?

>  		regmap_config = &cs35l63_regmap_sdw;
>  		break;
>  	default:
> @@ -510,6 +511,7 @@ static const struct sdw_device_id cs35l56_sdw_id[] = {
>  	SDW_SLAVE_ENTRY(0x01FA, 0x3556, 0x3556),
>  	SDW_SLAVE_ENTRY(0x01FA, 0x3557, 0x3557),
>  	SDW_SLAVE_ENTRY(0x01FA, 0x3563, 0x3563),
> +	SDW_SLAVE_ENTRY(0x01FA, 0x3562, 0x3562),

same here, the devices were in increasing order until this patch.

>  	{},
>  };
>  MODULE_DEVICE_TABLE(sdw, cs35l56_sdw_id);
> diff --git a/sound/soc/codecs/cs35l56-shared.c b/sound/soc/codecs/cs35l56-shared.c
> index d5817e4208479..f20bcdfd35af0 100644
> --- a/sound/soc/codecs/cs35l56-shared.c
> +++ b/sound/soc/codecs/cs35l56-shared.c
> @@ -96,6 +96,7 @@ int cs35l56_set_patch(struct cs35l56_base *cs35l56_base)
>  					    ARRAY_SIZE(cs35l56_patch_fw));
>  		break;
>  	case 0x63:
> +	case 0x62:

and here...


>  	case 0x35A630:
> +	case 0x35A620:

here as well

Maybe it's because the 62 support comes later, but no one will remember
this timeline and the code looks odd to me.

  reply	other threads:[~2026-07-17 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 12:01 [PATCH 0/2] ASoC: cs35l56: Add support for CS35L62 Richard Fitzgerald
2026-07-15 12:01 ` [PATCH 1/2] ASoC: cs35l56: Add support for CS35L62 for SoundWire Richard Fitzgerald
2026-07-17 20:38   ` Pierre-Louis Bossart [this message]
2026-07-15 12:01 ` [PATCH 2/2] ASoC: sdw_utils: Add codec info for CS35L62 Richard Fitzgerald

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=df0e5e52-7c34-4d09-9de1-eafe0405c951@linux.dev \
    --to=pierre-louis.bossart@linux.dev \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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