From: Thara Gopinath <thara.gopinath@linaro.org>
To: linux-arm-msm@vger.kernel.org, agross@kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
bjorn.andersson@linaro.org, amit.kucheria@linaro.org,
vinod.koul@linaro.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [Patch v2 0/2] Add support for AOSS resources that are used to warm up the SoC
Date: Tue, 30 Jul 2019 11:24:41 -0400 [thread overview]
Message-ID: <1564500283-16038-1-git-send-email-thara.gopinath@linaro.org> (raw)
The Always On Sub System (AOSS) hosts certain resources
that are used to warm up the soc if the temperature falls
below certain threshold. These resources are
added can be considered as thermal warming devices
(opposite of thermal cooling devices).
These resources are controlled via AOSS QMP protocol
In kernel, these devices can be treated the same way as any other
thermal cooling device and hence are registered with the thermal
cooling framework.
To use these resources as warming devices require further tweaks in
the thermal framework which are out of scope of this patch series.
Thara Gopinath (2):
soc: qcom: Extend AOSS QMP driver to support resources that are used
to wake up the SoC.
arm64: dts: qcom: Extend AOSS QMP node
arch/arm64/boot/dts/qcom/sdm845.dtsi | 8 +++
drivers/soc/qcom/qcom_aoss.c | 131 +++++++++++++++++++++++++++++++++++
2 files changed, 139 insertions(+)
--
2.1.4
next reply other threads:[~2019-07-30 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 15:24 Thara Gopinath [this message]
2019-07-30 15:24 ` [Patch v2 1/2] soc: qcom: Extend AOSS QMP driver to support resources that are used to wake up the SoC Thara Gopinath
2019-07-30 15:24 ` [Patch v2 2/2] arm64: dts: qcom: Extend AOSS QMP node Thara Gopinath
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=1564500283-16038-1-git-send-email-thara.gopinath@linaro.org \
--to=thara.gopinath@linaro.org \
--cc=agross@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vinod.koul@linaro.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).