From: Sudeep Holla <sudeep.holla@arm.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@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: Mon, 1 Aug 2022 10:59:10 +0100 [thread overview]
Message-ID: <20220801095910.ngexid57qgmvhes7@bogus> (raw)
In-Reply-To: <7d9607ed-f8eb-f3a2-22e4-4d2a240919c9@gmail.com>
On Fri, Jul 29, 2022 at 11:45:10AM -0700, Florian Fainelli wrote:
>
> Yes I would agree with both of those points, in fact, I would go one step
> further and add the ability to probe an arbitrary PSCI function ID, since
> deployed firmware typically go beyond the standard PSCI scope and implement
> a variety of custom extensions (at least we do).
>
Technically they must not be PSCI right ? Also I hope they are not using
Arm Architecture/CPU service range of FID and they use SiP/OEM service
range. From what I understand, you need a generic debug FS for all
SMCCC instead of just PSCI in your case. The latter must cover PSCI as
well while the reverse must not happen.
So if we need this beyond PSCI FID range, better you have it as generic
SMCCC debug FS. Thoughts ?
--
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-08-01 10:00 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 [this message]
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
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=20220801095910.ngexid57qgmvhes7@bogus \
--to=sudeep.holla@arm.com \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=f.fainelli@gmail.com \
--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