From: Mark Brown <broonie@kernel.org>
To: phucduc.bui@gmail.com
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
rafael@kernel.org, Danilo Krummrich <dakr@kernel.org>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev
Subject: Re: [PATCH] regcache: disable cache_only before rewriting paging registers
Date: Mon, 13 Jul 2026 12:58:24 +0100 [thread overview]
Message-ID: <24ce60c7-5539-4fba-8bf3-3a10875c3b75@sirena.org.uk> (raw)
In-Reply-To: <20260713073059.47914-1-phucduc.bui@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On Mon, Jul 13, 2026 at 02:30:58PM +0700, phucduc.bui@gmail.com wrote:
> From: bui duc phuc <phucduc.bui@gmail.com>
>
> cache_only must be disabled before re-writing the paging selector
> registers. Otherwise, _regmap_write() would update only the cache
> and return without calling map->reg_write(), leaving the selector
> register on the hardware unwritten and out of sync with the cache.
No, any access to the hardware is buggy - the whole point of cache only
mode is that we can't access the hardware. The paging register is part
of the context that needs to be rewritten when resyncing the cache.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-07-13 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 7:30 phucduc.bui
2026-07-13 11:58 ` Mark Brown [this message]
2026-07-13 13:07 ` Bui Duc Phuc
2026-07-13 13:43 ` Mark Brown
2026-07-13 14:59 ` Bui Duc Phuc
2026-07-13 15:06 ` Mark Brown
2026-07-13 21:58 ` Bui Duc Phuc
2026-07-14 11:23 ` Mark Brown
2026-07-14 23:02 ` Bui Duc Phuc
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=24ce60c7-5539-4fba-8bf3-3a10875c3b75@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phucduc.bui@gmail.com \
--cc=rafael@kernel.org \
/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