All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dong Aisheng <aisheng.dong@nxp.com>
Cc: linux-kernel@vger.kernel.org, dongas86@gmail.com,
	l.stach@pengutronix.de, peng.fan@nxp.com, shawnguo@kernel.org
Subject: Re: [PATCH RFC 1/2] regmap: add option to disable debugfs
Date: Mon, 20 Jun 2022 16:05:54 +0100	[thread overview]
Message-ID: <YrCM0reni+x/KWsG@sirena.org.uk> (raw)
In-Reply-To: <20220620134758.1286480-2-aisheng.dong@nxp.com>

[-- Attachment #1: Type: text/plain, Size: 865 bytes --]

On Mon, Jun 20, 2022 at 09:47:57PM +0800, Dong Aisheng wrote:
> The regmap core will create debugfs by default for each instance.
> However, it's fairly possible that some devices may not work properly
> with regmap registers dump via debugfs due to it may be in suspend
> state (e.g. Power domain is off).
> 
> Current regmap core does not support runtime pm for MMIO bus.
> Although there have been several retries [1] in community but finally
> didn't get accepted.
> 
> This patch adds an option to allow drivers to claim no debugfs support
> due to possible platform limitations.
> 
> 1. Link: https://lkml.iu.edu/hypermail/linux/kernel/1204.0/01646.html

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-06-20 15:16 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 [this message]
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
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=YrCM0reni+x/KWsG@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.