From: Evan Green <evgreen@chromium.org>
To: Lina Iyer <ilina@codeaurora.org>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
Rajendra Nayak <rnayak@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-kernel@vger.kernel.org, sboyd@kernel.org
Subject: Re: [PATCH v4 05/10] drivers: qcom: rpmh-rsc: write sleep/wake requests to TCS
Date: Sat, 17 Mar 2018 00:35:55 +0000 [thread overview]
Message-ID: <CAE=gft4YRzsG4w2oTFwSbxXtO4mNFo+SzntJo9ZP8Mm_N2Z6fg@mail.gmail.com> (raw)
In-Reply-To: <20180309232543.24636-6-ilina@codeaurora.org>
On Fri, Mar 9, 2018 at 3:27 PM Lina Iyer <ilina@codeaurora.org> wrote:
> Sleep and wake requests are sent when the application processor
> subsystem of the SoC is entering deep sleep states like in suspend.
> These requests help lower the system power requirements when the
> resources are not in use.
> Sleep and wake requests are written to the TCS slots but are not
> triggered at the time of writing. The TCS are triggered by the firmware
> after the last of the CPUs has executed its WFI. Since these requests
> may come in different batches of requests, it is the job of this
> controller driver to find and arrange the requests into the available
> TCSes.
> Signed-off-by: Lina Iyer <ilina@codeaurora.org>
> ---
> drivers/soc/qcom/rpmh-internal.h | 9 ++-
> drivers/soc/qcom/rpmh-rsc.c | 120
+++++++++++++++++++++++++++++++++++++++
> 2 files changed, 128 insertions(+), 1 deletion(-)
Reviewed-by: Evan Green <evgreen@chromium.org>
next prev parent reply other threads:[~2018-03-17 0:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 23:25 [PATCH v4 00/10] drivers/qcom: add RPMH communication support Lina Iyer
2018-03-09 23:25 ` [PATCH v4 01/10] drivers: qcom: rpmh-rsc: add RPMH controller for QCOM SoCs Lina Iyer
2018-03-09 23:25 ` [PATCH v4 02/10] dt-bindings: introduce RPMH RSC bindings for Qualcomm SoCs Lina Iyer
2018-03-26 22:22 ` Rob Herring
2018-03-09 23:25 ` [PATCH v4 03/10] drivers: qcom: rpmh-rsc: log RPMH requests in FTRACE Lina Iyer
2018-03-09 23:52 ` Steven Rostedt
2018-03-10 4:47 ` Lina Iyer
2018-03-09 23:25 ` [PATCH v4 04/10] drivers: qcom: rpmh: add RPMH helper functions Lina Iyer
2018-03-09 23:25 ` [PATCH v4 05/10] drivers: qcom: rpmh-rsc: write sleep/wake requests to TCS Lina Iyer
2018-03-17 0:35 ` Evan Green [this message]
2018-03-09 23:25 ` [PATCH v4 06/10] drivers: qcom: rpmh-rsc: allow invalidation of sleep/wake TCS Lina Iyer
2018-03-09 23:25 ` [PATCH v4 07/10] drivers: qcom: rpmh: cache sleep/wake state requests Lina Iyer
2018-03-17 0:36 ` Evan Green
2018-03-09 23:25 ` [PATCH v4 08/10] drivers: qcom: rpmh: allow requests to be sent asynchronously Lina Iyer
2018-03-09 23:25 ` [PATCH v4 09/10] drivers: qcom: rpmh: add support for batch RPMH request Lina Iyer
2018-03-17 0:36 ` Evan Green
2018-03-09 23:25 ` [PATCH v4 10/10] drivers: qcom: rpmh-rsc: allow active requests from wake TCS Lina Iyer
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='CAE=gft4YRzsG4w2oTFwSbxXtO4mNFo+SzntJo9ZP8Mm_N2Z6fg@mail.gmail.com' \
--to=evgreen@chromium.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).