Linux Sound subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Charles Keepax" <ckeepax@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, mfd@lists.linux.dev, lee@kernel.org
Subject: Re: [PATCH 1/2] mfd: cs42l43: Add load detection register needed for cs42l43b
Date: Wed, 11 Nov 2026 17:36:48 +0000	[thread overview]
Message-ID: <sashiko-outbox-209423@kernel.org> (raw)
In-Reply-To: <20261111171032.1491717-2-ckeepax@opensource.cirrus.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] mfd: cs42l43: missing CS42L43B_LOAD_DET_SEL in
  cs42l43_readable_register()
--

commit 86bb228eefe713b198f8b6a31cc740c008b39cd7
Author: Charles Keepax <ckeepax@opensource.cirrus.com>

mfd: cs42l43: Add load detection register needed for cs42l43b

This commit defines the CS42L43B_LOAD_DET_SEL register and marks it as
precious in cs42l43_precious_register().

> diff --git a/drivers/mfd/cs42l43.c b/drivers/mfd/cs42l43.c
> index a83b62064dae6..4e5d82c355ee3 100644
> --- a/drivers/mfd/cs42l43.c
> +++ b/drivers/mfd/cs42l43.c
> @@ -425,6 +425,7 @@ bool cs42l43_precious_register(struct device *dev, unsigned int reg)
>  	case CS42L43_RX_DATA:
>  	case CS42L43_DECIM_INT ... CS42L43_HPOUT_INT:
>  	case CS42L43_MCU_SW_REV ... CS42L43_MCU_RAM_MAX:
> +	case CS42L43B_LOAD_DET_SEL:
>  		return true;

[Severity: Medium]
Should CS42L43B_LOAD_DET_SEL also be added to cs42l43_readable_register()?

regmap_precious() and regmap_volatile() return false before invoking
cs42l43_precious_register() or cs42l43_volatile_register() when
cs42l43_readable_register() returns false.  As a result, writes to
CS42L43B_LOAD_DET_SEL during headphone load detection are treated as
non-volatile, cached in the maple tree regcache, and replayed to hardware on
every runtime PM resume during regcache_sync().

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261111171032.1491717-1-ckeepax@opensource.cirrus.com?part=1

  reply	other threads:[~2026-11-11 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 17:10 [PATCH 0/2] Update cs42l43b load detection proceedure Charles Keepax
2026-11-11 17:10 ` [PATCH 1/2] mfd: cs42l43: Add load detection register needed for cs42l43b Charles Keepax
2026-11-11 17:36   ` sashiko-bot [this message]
2026-11-11 17:10 ` [PATCH 2/2] ASoC: cs42l43: Update load detect procedure " Charles Keepax
2026-11-11 17:47   ` sashiko-bot
2026-11-12 11:22     ` Charles Keepax

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=sashiko-outbox-209423@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=lee@kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mfd@lists.linux.dev \
    --cc=sashiko-reviews@lists.linux.dev \
    /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