linux-kernel - Re: [PATCH v4 05/10] drivers: qcom: rpmh-rsc: write sleep/wake requests to TCS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 17 Mar 2018 00:35:55 +0000
From:   Evan Green <evgreen@...omium.org>
To:     Lina Iyer <ilina@...eaurora.org>
Cc:     Andy Gross <andy.gross@...aro.org>,
        David Brown <david.brown@...aro.org>,
        linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
        Rajendra Nayak <rnayak@...eaurora.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        linux-kernel@...r.kernel.org, sboyd@...nel.org
Subject: Re: [PATCH v4 05/10] drivers: qcom: rpmh-rsc: write sleep/wake
 requests to TCS

On Fri, Mar 9, 2018 at 3:27 PM Lina Iyer <ilina@...eaurora.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@...eaurora.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@...omium.org>