From: Mark Brown <broonie@kernel.org>
To: Dong Aisheng <dongas86@gmail.com>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
Peng Fan <peng.fan@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>
Subject: Re: [PATCH RFC 1/2] regmap: add option to disable debugfs
Date: Wed, 22 Jun 2022 13:36:30 +0100 [thread overview]
Message-ID: <YrMMzizzE7rIji5x@sirena.org.uk> (raw)
In-Reply-To: <CAA+hA=RQVRHzdy_ZpwcC-ZB8mwUYuMYu_iLNAfuPcMCS1G9WXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
On Wed, Jun 22, 2022 at 06:12:49PM +0800, Dong Aisheng wrote:
> NOTE: i didn't fix _regmap_write() as i.MX controls regmap write well in driver
> with power enabled first, so don't have issues in reality.
I can't tell what you think the problem is with _regmap_write()?
> It can be fixed in a separate patch later if needed.
> You may check if it's as your expected solution.
> For syscon, I still have no idea how to fix it if I can't disable it.
>
> diff --git a/drivers/base/regmap/regcache.c b/drivers/base/regmap/regcache.c
> index 2eaffd3224c9..da1702fd57cc 100644
> --- a/drivers/base/regmap/regcache.c
> +++ b/drivers/base/regmap/regcache.c
> @@ -495,7 +495,7 @@ EXPORT_SYMBOL_GPL(regcache_drop_region);
> void regcache_cache_only(struct regmap *map, bool enable)
> {
> map->lock(map->lock_arg);
> - WARN_ON(map->cache_bypass && enable);
> +// WARN_ON(map->cache_bypass && enable);
> map->cache_only = enable;
> trace_regmap_cache_only(map, enable);
> map->unlock(map->lock_arg);
What is the purpose of this change? Why would the combination of cache
only and bypass modes work be a good idea, and how should things behave
in that case?
> diff --git a/drivers/soc/imx/imx8m-blk-ctrl.c b/drivers/soc/imx/imx8m-blk-ctrl.c
> index 7ebc28709e94..12f0f9a24fad 100644
> --- a/drivers/soc/imx/imx8m-blk-ctrl.c
> +++ b/drivers/soc/imx/imx8m-blk-ctrl.c
The changes in here look reasonable, though I'm not familiar with this
driver so might be missing something.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-22 12:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 13:47 [PATCH RFC 0/2] regmap: option to disable debugfs Dong Aisheng
2022-06-20 13:47 ` [PATCH RFC 1/2] regmap: add " Dong Aisheng
2022-06-20 15:05 ` Mark Brown
2022-06-20 15:47 ` Aisheng Dong
2022-06-20 15:49 ` Mark Brown
2022-06-20 16:15 ` Aisheng Dong
2022-06-20 17:51 ` Mark Brown
2022-06-21 14:56 ` Aisheng Dong
2022-06-21 15:31 ` Mark Brown
2022-06-21 18:16 ` Aisheng Dong
2022-06-22 8:08 ` Lucas Stach
2022-06-22 8:18 ` Aisheng Dong
2022-06-22 8:35 ` Lucas Stach
2022-06-22 12:25 ` Mark Brown
2022-06-22 10:12 ` Dong Aisheng
2022-06-22 12:36 ` Mark Brown [this message]
2022-06-22 16:05 ` Dong Aisheng
2022-06-22 16:27 ` Mark Brown
2022-06-22 16:42 ` Dong Aisheng
2022-06-22 16:48 ` Mark Brown
2022-06-22 17:01 ` Dong Aisheng
2022-06-22 17:07 ` Mark Brown
2022-06-20 13:47 ` [PATCH RFC 2/2] soc: imx8m-blk-ctrl: do not export debugfs Dong Aisheng
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=YrMMzizzE7rIji5x@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=dongas86@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.