From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Fix illegal writes to OTP_MEM registers
Date: Wed, 29 Apr 2026 08:23:15 +0900 [thread overview]
Message-ID: <afFBY3BuBbScZdu2@sirena.co.uk> (raw)
In-Reply-To: <20260428115228.158252-1-rf@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
On Tue, Apr 28, 2026 at 12:52:28PM +0100, Richard Fitzgerald wrote:
> These registers hold a constant, and originally they were marked as
> readable non-volatile so that this value would be read into the regmap
> cache. The problem with this is regcache_sync() issues a write for any
> cached register that does not have a reg_default.
This feels like something that's common enough to be worth teaching the
regmap core about.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-28 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 11:52 [PATCH] ASoC: cs35l56: Fix illegal writes to OTP_MEM registers Richard Fitzgerald
2026-04-28 23:23 ` Mark Brown [this message]
2026-04-28 23:41 ` 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=afFBY3BuBbScZdu2@sirena.co.uk \
--to=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