From: Stephen Boyd <swboyd@chromium.org>
To: Andy Gross <agross@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rajeshwari <rkambl@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sivaa@codeaurora.org,
sanm@codeaurora.org, Rajeshwari <rkambl@codeaurora.org>,
Amit Kucheria <amit.kucheria@linaro.org>
Subject: Re: [PATCH 1/1] arm64: dts: qcom: sc7180: Add device node support for TSENS in SC7180
Date: Mon, 04 Nov 2019 13:44:27 -0800 [thread overview]
Message-ID: <5dc09bbb.1c69fb81.196e5.9770@mx.google.com> (raw)
In-Reply-To: <1572610108-1363-2-git-send-email-rkambl@codeaurora.org>
Quoting Rajeshwari (2019-11-01 05:08:28)
> diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi b/arch/arm64/boot/dts/qcom/sc7180.dtsi
> index 07ea393..06ded1d 100644
> --- a/arch/arm64/boot/dts/qcom/sc7180.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi
> @@ -449,6 +465,508 @@
> };
> };
>
> + thermal-zones {
> + aoss-0-usr {
> + polling-delay-passive = <0>;
> + polling-delay = <0>;
Can we get real polling delays instead of 0?
> + thermal-governor = "user_space";
> + thermal-sensors = <&tsens0 0>;
> + wake-capable-sensor;
What is this property?
> + trips {
> + active-config0 {
> + temperature = <125000>;
> + hysteresis = <1000>;
> + type = "passive";
> + };
> + reset-mon-cfg {
> + temperature = <115000>;
> + hysteresis = <5000>;
> + type = "passive";
> + };
> + };
> + };
> +
> + cpu-0-0-usr {
> + polling-delay-passive = <0>;
> + polling-delay = <0>;
> + thermal-governor = "user_space";
What is this property?
next prev parent reply other threads:[~2019-11-04 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 12:08 [PATCH 0/1] Add device node support for TSENS Rajeshwari
2019-11-01 12:08 ` [PATCH 1/1] arm64: dts: qcom: sc7180: Add device node support for TSENS in SC7180 Rajeshwari
2019-11-04 21:44 ` Stephen Boyd [this message]
2019-11-05 14:51 ` Amit Kucheria
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=5dc09bbb.1c69fb81.196e5.9770@mx.google.com \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=amit.kucheria@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=rkambl@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sanm@codeaurora.org \
--cc=sivaa@codeaurora.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).