From: Deepak Kumar Singh <deesin@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>,
bjorn.andersson@linaro.org, clew@codeaurora.org,
sibis@codeaurora.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-remoteproc@vger.kernel.org, Andy Gross <agross@kernel.org>
Subject: Re: [PATCH V5 2/2] soc: qcom: aoss: Add debugfs entry
Date: Mon, 30 Aug 2021 17:16:53 +0530 [thread overview]
Message-ID: <ff8ede00-008e-4dfb-7a39-19242d421462@codeaurora.org> (raw)
In-Reply-To: <CAE-0n50CM=DpXx7fzrcnWox+ZSfqvWuEb-R_rTP8ghR+bd54eA@mail.gmail.com>
On 8/5/2021 11:58 PM, Stephen Boyd wrote:
> Quoting Deepak Kumar Singh (2021-08-05 04:12:54)
>> It can be useful to control the different power states of various
>> parts of hardware for device testing. Add a debugfs node for qmp so
>> messages can be sent to aoss for debugging and testing purposes.
> Is it ever useful after device testing? I'd prefer we not apply this
> patch as it looks like testing code that won't ever be used after
> developing this driver.
This is not only for testing. Some user space clients can also use this
to send messages to aoss.
One such example is setting higher ddr frequency during boot and
reducing it post boot from user space.
next prev parent reply other threads:[~2021-08-30 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 11:12 [PATCH V5 0/2] qcom aoss qmp_get and debugfs support patches Deepak Kumar Singh
2021-08-05 11:12 ` [PATCH V5 1/2] soc: qcom: aoss: Expose send for generic usecase Deepak Kumar Singh
2021-08-05 18:34 ` Stephen Boyd
2021-08-09 9:57 ` Deepak Kumar Singh
2021-08-09 17:56 ` Stephen Boyd
2021-08-05 11:12 ` [PATCH V5 2/2] soc: qcom: aoss: Add debugfs entry Deepak Kumar Singh
2021-08-05 18:28 ` Stephen Boyd
2021-08-30 11:46 ` Deepak Kumar Singh [this message]
2021-08-30 23:01 ` Stephen Boyd
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=ff8ede00-008e-4dfb-7a39-19242d421462@codeaurora.org \
--to=deesin@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=clew@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=sibis@codeaurora.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).