From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Hongyang Zhao <hongyang.zhao@thundersoft.com>
Cc: andersson@kernel.org, casey.connolly@linaro.org,
christopher.obbard@linaro.org, linux-arm-msm@vger.kernel.org,
loic.minier@oss.qualcomm.com, rosh@debian.org
Subject: Re: [PATCH v4 1/2] arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts
Date: Wed, 22 Oct 2025 18:47:36 +0200 [thread overview]
Message-ID: <dddbb37d-04a2-4f16-a9e8-cdad503c033c@oss.qualcomm.com> (raw)
In-Reply-To: <20251009103041.22568-1-hongyang.zhao@thundersoft.com>
On 10/9/25 12:30 PM, Hongyang Zhao wrote:
>> On 9/30/25 6:32 AM, Hongyang Zhao wrote:
>>> Add DTS for Thundercomm qcs6490-rubikpi3 board which uses
>>> QCS6490 SoC.
>>>
>>> Works:
>>> - Wi-Fi (AP6256)
>>> - Bluetooth (AP6256)
>>> - Ethernet (AX88179B connected to UPD720201)
>>> - USB Type-C
>>> - USB Type-A 2.0 port
>>> - Two USB Type-A 3.0 ports (UPD720201 connected to PCIe0)
>>> - M.2 M-Key 2280 PCIe 3.0
>>> - RTC
>>> - 40PIN: I2C x1, UART x1
>>>
>>> Signed-off-by: Hongyang Zhao <hongyang.zhao@thundersoft.com>
>>> Reviewed-by: Roger Shimizu <rosh@debian.org>
>>> Cc: Casey Connolly <casey.connolly@linaro.org>
>>> Cc: Christopher Obbard <christopher.obbard@linaro.org>
>>> Cc: Loic Minier V1<loic.minier@oss.qualcomm.com>
[...]
>>> +&thermal_zones {
>>> + cpu0-thermal {
>>> + trips {
>>> + cpu_tepid: cpu-tepid {
>>> + temperature = <65000>;
>>> + hysteresis = <5000>;
>>> + type = "active";
>>> + };
>>
>> these are not useful unless you wire up the fan here
>
> I wrote a service program at the user levelthat listens for netlink messages
> from here to control the fan.
Creative!
> Controlling the fan at the kernel level should be a better approach,
> and I have verified this. I will make modifications similar to the following:
>
> cpu0-thermal {
> trips {
> cpu_tepid: cpu-tepid {
> temperature = <65000>;
> hysteresis = <5000>;
> type = "active";
> };
>
> cpu_warm: cpu-warm {
> temperature = <80000>;
> hysteresis = <5000>;
> type = "active";
> };
>
> cpu_hot: cpu-hot {
> temperature = <90000>;
> hysteresis = <5000>;
> type = "active";
> };
> };
>
> cooling-maps {
> map-cpu-tepid {
> /* active: set fan to cooling level 1 */
> cooling-device = <&fan0 1 1>;
> trip = <&cpu_tepid>;
> };
>
> map-cpu-warm {
> /* active: set fan to cooling level 2 */
> cooling-device = <&fan0 2 2>;
> trip = <&cpu_warm>;
> };
>
> map-cpu-hot {
> /* active: set fan to cooling level 3 */
You can drop these comments
Konrad
next prev parent reply other threads:[~2025-10-22 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 4:32 [PATCH v4 0/2] arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts Hongyang Zhao
2025-09-30 4:32 ` [PATCH v4 1/2] " Hongyang Zhao
2025-10-06 10:33 ` Konrad Dybcio
2025-10-09 10:30 ` Hongyang Zhao
2025-10-22 16:47 ` Konrad Dybcio [this message]
2025-10-30 2:21 ` Hongyang Zhao
2025-09-30 4:32 ` [PATCH v4 2/2] dt-bindings: arm: qcom: rubikpi3: document rubikpi3 board binding Hongyang Zhao
2025-09-30 5:30 ` Dmitry Baryshkov
2025-09-30 6:26 ` Hongyang Zhao
2025-10-06 8:53 ` Krzysztof Kozlowski
2025-10-09 11:05 ` [PATCH v4 2/2] arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts Hongyang Zhao
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=dddbb37d-04a2-4f16-a9e8-cdad503c033c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=christopher.obbard@linaro.org \
--cc=hongyang.zhao@thundersoft.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.minier@oss.qualcomm.com \
--cc=rosh@debian.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