From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Sibi Sankar <sibis@codeaurora.org>
Subject: Re: [PATCH v2 00/13] qcom: dts: thermal cleanups
Date: Tue, 23 Apr 2019 15:10:35 +0200 [thread overview]
Message-ID: <903fa0a6-5c40-97b4-1c01-fd84f3e51c62@free.fr> (raw)
In-Reply-To: <CAP245DVqGQ6MEfcYjr2PYnD=BR86vC=BsRMpZe0jsgbAc6jFGg@mail.gmail.com>
On 23/04/2019 14:56, Amit Kucheria wrote:
> On Tue, Apr 23, 2019 at 3:01 PM Marc Gonzalez wrote:
>
>> On 02/04/2019 20:46, Amit Kucheria wrote:
>>
>>> On Tue, Apr 2, 2019 at 8:58 PM Marc Gonzalez wrote:
>>>
>>>> On 29/03/2019 11:12, Amit Kucheria wrote:
>>>>
>>>>> Changes since v1:
>>>>> - Devices that are not associated with cooling-maps use the 'hot' type
>>>>> - Remove critical trip from such devices too and restrict that type of CPUs
>>>>> - For 8916, add the sensor on the modem
>>>>>
>>>>> Description:
>>>>> - Expose all temperature sensors on msm8916, msm996, msm8998, sdm845
>>>>> - split up the register address map for msm8998
>>>>> - standardize names of the various thermal-zones across boards to make it
>>>>> easy for test scripts to parse
>>>>
>>>> This is what I see on msm8998 with your patch series applied on top of
>>>> yesterday's next:
>>>>
>>>> # dmesg | grep of_parse_thermal_zones
>>>> of_parse_thermal_zones: build cpu0-thermal zone 0
>>>> of_parse_thermal_zones: build cpu1-thermal zone 0
>>>> of_parse_thermal_zones: build cpu2-thermal zone 0
>>>> of_parse_thermal_zones: build cpu3-thermal zone 0
>>>> of_parse_thermal_zones: build cpu4-thermal zone 0
>>>> of_parse_thermal_zones: build cpu5-thermal zone 0
>>>> of_parse_thermal_zones: build cpu6-thermal zone 0
>>>> of_parse_thermal_zones: build cpu7-thermal zone 0
>>>> of_parse_thermal_zones: build gpu-thermal-bottom zone 0
>>>> of_parse_thermal_zones: build gpu-thermal-top zone 0
>>>> of_parse_thermal_zones: build cluster0-mhm-thermal zone -22
>>>> of_parse_thermal_zones: build cluster1-mhm-thermal zone -22
>>>> of_parse_thermal_zones: build cluster1-l2-thermal zone 0
>>>> of_parse_thermal_zones: build modem-thermal zone 0
>>>> of_parse_thermal_zones: build mem-thermal zone 0
>>>> of_parse_thermal_zones: build wlan-thermal zone 0
>>>> of_parse_thermal_zones: build q6-dsp-thermal zone 0
>>>> of_parse_thermal_zones: build camera-thermal zone 0
>>>> of_parse_thermal_zones: build multimedia-thermal zone 0
>>>> of_parse_thermal_zones: build pm8998 zone 0
>>>> of_parse_thermal_zones: build battery-thermal zone 0
>>>> of_parse_thermal_zones: build skin-thermal zone 0
>>>>
>>>> NB: -EINVAL for cluster0-mhm-thermal and cluster1-mhm-thermal
>>>>
>>>>
>>>> # cat /sys/devices/virtual/thermal/thermal_zone*/temp
>>>> 35800
>>>> 35200
>>>> 34500
>>>> 34800
>>>> 34500
>>>> 34100
>>>> 34100
>>>> 33500
>>>> 33800
>>>> cat: /sys/devices/virtual/thermal/thermal_zone17/temp: Invalid argument
>>>> 36100
>>>> cat: /sys/devices/virtual/thermal/thermal_zone19/temp: Invalid argument
>>>> 35500
>>>> 36100
>>>> 35800
>>>> 35200
>>>> 35500
>>>> 36100
>>>> cat: /sys/devices/virtual/thermal/thermal_zone8/temp: Invalid argument
>>>> cat: /sys/devices/virtual/thermal/thermal_zone9/temp: Invalid argument
>>>>
>>>>
>>>> Are the failures expected?
>>>> (cluster*-mhm-thermal and thermal_zone*/temp)
>>>
>>> No they are not. Unfortunately, I didn't have HW to test, so
>>> appreciate the help with testing. I'll check the 8, 9, 17 and 19 again
>>> before resubmitting.
>>
>> Looks like Andy merged this series?
>
> Argh! my bad, I completely forgot about the need to fix this up. I
> need to get me one of these boards.
>
>> https://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git/log/?h=for-next
>>
>> I was expecting a respin, or a discussion of the failures.
>>
>> Slightly confused. What next?
>
> We can either revert that one patch for the msm8998, but I think it
> might be better if I send a fixup patch that could fixup those 4 zones
> instead.
>
> Does that work for you?
Sure. I can give you a Tested-by once everything works on the MEDIABOX I have.
You mention the 4 thermal_zone*/temp failures.
What about the cluster0-mhm-thermal and cluster1-mhm-thermal failures?
Regards.
next prev parent reply other threads:[~2019-04-23 13:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 10:12 [PATCH v2 00/13] qcom: dts: thermal cleanups Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 01/13] arm64: dts: msm8998: thermal: split address space into two Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 02/13] arm64: dts: msm8998: efficiency is not valid property Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 03/13] arm64: dts: msm8916: thermal: Add sensor for modem Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 04/13] arm64: dts: msm8996: thermal: Add temperature sensors near major peripherals Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 05/13] arm64: dts: msm8998: thermal: Fix the cpu sensor numbers Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 06/13] arm64: dts: msm8998: thermal: Fix the gpu sensor number Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 07/13] arm64: dts: msm8998: thermal: GPU has two sensors, add the second Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 08/13] arm64: dts: msm8998: thermal: Add temperature sensors near major peripherals Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 09/13] arm64: dts: sdm845: " Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 10/13] arm64: dts: msm8998: thermal: Make trip names consistent Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 11/13] arm64: dts: msm8916: " Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 12/13] arm64: dts: msm8996: " Amit Kucheria
2019-03-29 10:12 ` [PATCH v2 13/13] arm64: dts: msm8916: thermal: Convert camera trip type to hot Amit Kucheria
2019-04-02 13:58 ` [PATCH v2 00/13] qcom: dts: thermal cleanups Marc Gonzalez
2019-04-02 18:46 ` Amit Kucheria
2019-04-23 9:31 ` Marc Gonzalez
2019-04-23 12:56 ` Amit Kucheria
2019-04-23 13:10 ` Marc Gonzalez [this message]
2019-04-24 14:30 ` Marc Gonzalez
2019-04-25 6:31 ` Amit Kucheria
2019-04-25 11:25 ` Marc Gonzalez
2019-04-25 12:02 ` Marc Gonzalez
2019-04-25 13:06 ` Marc Gonzalez
2019-04-25 13:16 ` Amit Kucheria
2019-04-23 19:14 ` Andy Gross
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=903fa0a6-5c40-97b4-1c01-fd84f3e51c62@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=agross@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sibis@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).