From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Marek Vasut <marex@denx.de>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/1] clk: rs9: Fix suspend/resume
Date: Tue, 14 Mar 2023 08:22:07 +0100 [thread overview]
Message-ID: <3227516.44csPzL39Z@steina-w> (raw)
In-Reply-To: <a794bd7b3ee514a508c2af3d2b594d10.sboyd@kernel.org>
Am Montag, 13. März 2023, 23:26:54 CET schrieb Stephen Boyd:
> Quoting Alexander Stein (2023-03-09 23:49:40)
>
> > Disabling the cache in commit 2ff4ba9e3702 ("clk: rs9: Fix I2C accessors")
> > without removing cache synchronization in resume path results in a
> > kernel panic as map->cache_ops is unset, due to REGCACHE_NONE.
> > Enable flat cache again to support resume again. num_reg_defaults_raw
> > is necessary to read the cache defaults from hardware. Some registers
> > are strapped in hardware and cannot be provided in software.
> >
> > Fixes: 2ff4ba9e3702 ("clk: rs9: Fix I2C accessors")
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> > ---
> > There is also a series to not panic when using regcache_sync on
> > REGCACHE_NONE maps at [1].
>
> And it was rejected?
v2 has been accepted and is available at [1] in regmap's for-next branch.
Best regards,
Alexander
[1] https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/
commit/?id=fd883d79e4dcd2417c2b80756f22a2ff03b0f6e0
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-03-14 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 7:49 [PATCH 1/1] clk: rs9: Fix suspend/resume Alexander Stein
2023-03-13 22:26 ` Stephen Boyd
2023-03-14 7:22 ` Alexander Stein [this message]
2023-03-20 19:35 ` Stephen Boyd
2023-03-21 6:20 ` Alexander Stein
2023-03-21 17:47 ` Stephen Boyd
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=3227516.44csPzL39Z@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=linux-clk@vger.kernel.org \
--cc=marex@denx.de \
--cc=mturquette@baylibre.com \
--cc=sboyd@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