From: Mark Brown <broonie@kernel.org>
To: Aisheng Dong <aisheng.dong@nxp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dongas86@gmail.com" <dongas86@gmail.com>,
"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: Mon, 20 Jun 2022 16:49:52 +0100 [thread overview]
Message-ID: <YrCXILblKsp6DuN3@sirena.org.uk> (raw)
In-Reply-To: <DB9PR04MB84779EF2842D789FA66094C380B09@DB9PR04MB8477.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On Mon, Jun 20, 2022 at 03:47:05PM +0000, Aisheng Dong wrote:
> > As indicated in the message you're linking to here if the device can't be
> > accessed it should be being put in cache only mode which will ensure that
> > nothing can do any physical accesses.
> I wonder that's not a stable solution assuming there're possible volatile registers.
> Isn't that?
The driver is going to need to power the device back up to access the
volatile registers so it can take the device out of cache only mode when
it's doing that can't it?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-20 15:50 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 [this message]
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
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=YrCXILblKsp6DuN3@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.