From: Sudeep Holla <sudeep.holla@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] firmware/psci: Add debugfs support to ease debugging
Date: Fri, 29 Jul 2022 12:49:46 +0100 [thread overview]
Message-ID: <20220729114946.jhjjmkw36vjdsyj3@bogus> (raw)
In-Reply-To: <YuKJtKHzoR4DUsOr@sirena.org.uk>
On Thu, Jul 28, 2022 at 02:05:56PM +0100, Mark Brown wrote:
> On Thu, Jul 28, 2022 at 10:08:06AM +0100, Sudeep Holla wrote:
> > On Wed, Jul 27, 2022 at 11:09:01PM +0300, Dmitry Baryshkov wrote:
>
> > > To ease debugging of PSCI supported features, add debugfs file called
> > > 'psci' describing PSCI and SMC CC versions
>
> > These 2 are for sure in the boot log. Having them is debugfs accessible
> > via file system add not much value as we would hit issues quite early in
> > the boot for most of the things related to PSCI.
>
> It can be useful to have something that can be queried at any point when
> collecting diagnostics, even if there's been a lot of logging or log
> rotation since boot. It makes it easier to give people instructions or
> a tool which will reliably collect useful information when filing a bug
> report.
Fair enough. I agree this is will be useful to debug/analyse non boot
issues.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-29 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 20:09 [PATCH] firmware/psci: Add debugfs support to ease debugging Dmitry Baryshkov
2022-07-27 20:15 ` Bhupesh Sharma
2022-07-27 20:53 ` Dmitry Baryshkov
2022-07-27 20:55 ` Bhupesh Sharma
2022-07-27 20:56 ` Dmitry Baryshkov
2022-07-27 20:59 ` Bhupesh Sharma
2022-07-27 21:03 ` Dmitry Baryshkov
2022-07-28 9:08 ` Sudeep Holla
2022-07-28 9:20 ` Dmitry Baryshkov
2022-07-29 18:45 ` Florian Fainelli
2022-08-01 9:59 ` Sudeep Holla
2022-08-01 12:14 ` Mark Brown
2022-08-01 13:30 ` Sudeep Holla
2022-07-28 13:05 ` Mark Brown
2022-07-29 11:49 ` Sudeep Holla [this message]
2022-07-28 13:38 ` Mark Brown
2022-07-29 14:55 ` Dmitry Baryshkov
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=20220729114946.jhjjmkw36vjdsyj3@bogus \
--to=sudeep.holla@arm.com \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
/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