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 17:48:51 +0100 [thread overview]
Message-ID: <YrNH8/eaYHYeAWNJ@sirena.org.uk> (raw)
In-Reply-To: <CAA+hA=SHgp1jZn1Qwrcu3fMnn22aaVimS4+Y2hPcWehS4zdRoA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
On Thu, Jun 23, 2022 at 12:42:51AM +0800, Dong Aisheng wrote:
> On Thu, Jun 23, 2022 at 12:27 AM Mark Brown <broonie@kernel.org> wrote:
> > cache_bypass is only going to be true if something enabled bypass, why
> > would a device that doesn't use a cache enable bypass? It does get
> > turned on transiently by things like patching but those only make sense
> > if the device can be accessed so caceh_only shouldn't be on then.
> It was enabled by default according to the code:
> __regmap_init -> regcache_init
Ah, right. That makes sense - we should relax the check to only apply
if there is actually a cache.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-22 16:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 13:47 [PATCH RFC 0/2] regmap: " 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
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 [this message]
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=YrNH8/eaYHYeAWNJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®