Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>,
	Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	David Rhodes <david.rhodes@cirrus.com>,
	Vlad Karpovich <vkarpovi@opensource.cirrus.com>,
	Paul Handrigan <Paul.Handrigan@cirrus.com>,
	patches@opensource.cirrus.com, linux-sound@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/3] ASoC: cs35l41/cs35l45/cs4265: sort the reg_defaults tables
Date: Wed, 5 Aug 2026 14:25:52 +0300	[thread overview]
Message-ID: <272f965d-4265-4467-9cd0-20259e107eff@linux.intel.com> (raw)
In-Reply-To: <2585c2ec-1146-4a48-9169-274449d1bbda@opensource.cirrus.com>



On 05/08/2026 13:36, Richard Fitzgerald wrote:
> On 05/08/2026 11:17 am, Péter Ujfalusi wrote:
>>
>>
>> On 05/08/2026 13:10, Charles Keepax wrote:
>>>>> I don't think we need to sort them. Just fail, so that an unsorted
>>>>> table
>>>>> must be fixed.
>>>>
>>>> That would be a big regression all around the place, ordering w/ the
>>>> debug message if developer is interested is much better.
>>>
>>> I think I would come down between the two of you. I definitely
>>> agree with Richard on don't sort them, just encourages drivers to
>>> be wrong. But I also agree with you, don't hard fail. I would
>>> vote for just print an error message and carry on. That way no
>>> regressions, but also a nice big warning message to let people
>>> know what is wrong when they see problems.
>>
>> I usually try to avoid alarming/annoying users with error messages, on
>> the other hand I agree that w/o some pressure, these will never be
>> corrected at root either ;)
>>
>> On the yet another hand, if the regcache have means to fix this, it
>> might be put into use as well.
>> A dev_warn at max to get attention or info level perhaps and fixing it
>> up?
>>
> I asked Codex (GPT5) to search for all reg_default tables with out-of
> order entries or duplicate entries, looking only at those assigned to
> struct regmap_config.reg_defaults (some reg_defaults tables are used for
> patching - those are allowed to be out-of-order).
> 
> It came up with this:
> 
> Restricting results to tables referenced by struct
> regmap_config.reg_defaults, 39 files violate the rule:

and some of these have duplicate addresses with different default values.

I can send more fixes while I'm at this for the clear cases, for Cirrus,
Realtek and TI I have sent few patches.

> 
>   drivers/firmware/cirrus/test/cs_dsp_mock_regmap.c
>   drivers/leds/leds-lp50xx.c
>   drivers/mfd/cs42l43.c
>   drivers/platform/mellanox/mlx-platform.c
>   drivers/power/supply/bq25980_charger.c
>   sound/soc/codecs/ad1836.c
>   sound/soc/codecs/adau1373.c
>   sound/soc/codecs/adau1761.c
>   sound/soc/codecs/adau1781.c
>   sound/soc/codecs/cs35l41-lib.c
>   sound/soc/codecs/cs35l45-tables.c
>   sound/soc/codecs/cs4265.c
>   sound/soc/codecs/cx2072x.c
>   sound/soc/codecs/lm49453.c
>   sound/soc/codecs/max9860.c
>   sound/soc/codecs/ml26124.c
>   sound/soc/codecs/msm8916-wcd-analog.c
>   sound/soc/codecs/pcm512x.c
>   sound/soc/codecs/pm4125-sdw.c
>   sound/soc/codecs/rt1019.c
>   sound/soc/codecs/rt1318.c
>   sound/soc/codecs/rt274.c
>   sound/soc/codecs/rt286.c
>   sound/soc/codecs/rt298.c
>   sound/soc/codecs/rt700-sdw.h
>   sound/soc/codecs/rt711-sdw.h
>   sound/soc/codecs/rt715-sdw.h
>   sound/soc/codecs/sgtl5000.c
>   sound/soc/codecs/sti-sas.c
>   sound/soc/codecs/tas2552.c
>   sound/soc/codecs/tas2764.c
>   sound/soc/codecs/tas2780.c
>   sound/soc/codecs/tas675x.c
>   sound/soc/codecs/wm8996.c
>   sound/soc/fsl/fsl_easrc.c
>   sound/soc/tegra/tegra210_admaif.c
>   sound/soc/tegra/tegra210_i2s.c
>   sound/soc/tegra/tegra210_mbdrc.c
>   sound/soc/tegra/tegra210_mixer.c
> 

-- 
Péter


  reply	other threads:[~2026-08-05 11:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  8:24 [PATCH 0/3] ASoC: cs35l41/cs35l45/cs4265: sort the reg_defaults tables Peter Ujfalusi
2026-08-05  8:24 ` [PATCH 1/3] ASoC: cs35l41: sort the register default table Peter Ujfalusi
2026-08-05  9:58   ` Richard Fitzgerald
2026-08-05  8:24 ` [PATCH 2/3] ASoC: cs35l45: " Peter Ujfalusi
2026-08-05 11:35   ` Richard Fitzgerald
2026-08-05  8:24 ` [PATCH 3/3] ASoC: cs4265: " Peter Ujfalusi
2026-08-05 11:31   ` Richard Fitzgerald
2026-08-05  8:40 ` [PATCH 0/3] ASoC: cs35l41/cs35l45/cs4265: sort the reg_defaults tables Pierre-Louis Bossart
2026-08-05  8:52   ` Péter Ujfalusi
2026-08-05  8:59     ` Pierre-Louis Bossart
2026-08-05  9:00   ` Richard Fitzgerald
2026-08-05  9:10     ` Péter Ujfalusi
2026-08-05  9:25       ` Charles Keepax
2026-08-05  9:38         ` Richard Fitzgerald
2026-08-05  9:52           ` Charles Keepax
2026-08-05  9:52           ` Péter Ujfalusi
2026-08-05  9:56             ` Richard Fitzgerald
2026-08-05  9:59               ` Péter Ujfalusi
2026-08-05 10:10                 ` Charles Keepax
2026-08-05 10:17                   ` Péter Ujfalusi
2026-08-05 10:36                     ` Richard Fitzgerald
2026-08-05 11:25                       ` Péter Ujfalusi [this message]
2026-08-05 11:31                         ` Charles Keepax
2026-08-05 11:38                           ` Richard Fitzgerald
2026-08-05 11:38                           ` Péter Ujfalusi
2026-08-05  9:25     ` Péter Ujfalusi
2026-08-05 10:38   ` Mark Brown
2026-08-05  8:59 ` Charles Keepax
2026-08-05 12:37 ` 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=272f965d-4265-4467-9cd0-20259e107eff@linux.intel.com \
    --to=peter.ujfalusi@linux.intel.com \
    --cc=Paul.Handrigan@cirrus.com \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=david.rhodes@cirrus.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=rf@opensource.cirrus.com \
    --cc=stable@vger.kernel.org \
    --cc=vkarpovi@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