From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: [PATCH v4 0/3] regcache: Avoid accessing non-initialised cache
Date: Mon, 2 Mar 2026 10:56:54 +0100 [thread overview]
Message-ID: <20260302095847.2310066-1-andriy.shevchenko@linux.intel.com> (raw)
Refactor regcache flow that populates cache on initialisation phase
based on the values in HW. This makes code robust against any possible
accesses to not-fully initialised caches.
Changelog v4:
- made conditional against 'count' to make it less dependent to the previous code path
v3: 20260226135918.381979-1-andriy.shevchenko@linux.intel.com
Changelog v3:
- dropped unneeded churn in patch 3 (Mark)
- fixed code to pass kunit test cases (Mark)
v2: 20260225161659.3811671-1-andriy.shevchenko@linux.intel.com
Changelog v2:
- rebased on top of the latest regmap changes (Mark)
- added two more little cleanups (patches 4 & 5)
Andy Shevchenko (3):
regcache: Move HW readback after cache initialisation
regcache: Define iterator inside for-loop and align their types
regcache: Amend printf() specifiers when printing registers
drivers/base/regmap/internal.h | 2 +-
drivers/base/regmap/regcache.c | 42 ++++++++++++++++++++--------------
2 files changed, 26 insertions(+), 18 deletions(-)
--
2.50.1
next reply other threads:[~2026-03-02 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 9:56 Andy Shevchenko [this message]
2026-03-02 9:56 ` [PATCH v4 1/3] regcache: Move HW readback after cache initialisation Andy Shevchenko
2026-03-02 14:49 ` Mark Brown
2026-03-02 15:09 ` Andy Shevchenko
2026-03-02 9:56 ` [PATCH v4 2/3] regcache: Define iterator inside for-loop and align their types Andy Shevchenko
2026-03-02 9:56 ` [PATCH v4 3/3] regcache: Amend printf() specifiers when printing registers Andy Shevchenko
2026-03-03 11:20 ` [PATCH v4 0/3] regcache: Avoid accessing non-initialised cache 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=20260302095847.2310066-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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