From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] regmap: debugfs: runtime resume a device when reading registers
Date: Wed, 10 Jan 2024 13:46:31 +0100 [thread overview]
Message-ID: <7625183.EvYhyI6sBW@steina-w> (raw)
In-Reply-To: <3bc9c762-3573-4d8b-bfcf-6c8e91938dcd@sirena.org.uk>
Am Mittwoch, 10. Januar 2024, 13:23:17 CET schrieb Mark Brown:
> On Wed, Jan 10, 2024 at 10:53:58AM +0100, Alexander Stein wrote:
> > If the registers shall be read from device, runtime resume it in order
> > to enable a possiblly attached power domain before accessing the device.
>
> The idea is that the debugfs interface isn't supposed to be disruptive
> to the thing being debugged. It would be better to detect if there will
> be problems and report the status as busy.
In my case the device is actually unused, runtime suspended, thus disabled
power domain. That's totally different to busy. In this case dumping the
registers is non-disruptive, unless you account enabling/disabling the power
domain as well. Any attached clock is already enabled/disabled, but power
domains are not.
Best regards,
Alexander
--
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:[~2024-01-10 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 9:53 Alexander Stein
2024-01-10 12:23 ` Mark Brown
2024-01-10 12:46 ` Alexander Stein [this message]
2024-01-10 13:04 ` Mark Brown
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=7625183.EvYhyI6sBW@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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®