On Thu, Apr 25, 2019 at 6:36 PM Marc Gonzalez wrote:
>
> On 25/04/2019 08:31, Amit Kucheria wrote:
>
> > [PATCH 3/3] arm64: dts: msm8998: thermal: Restrict thermal zone name length
> > to under 20
> >
> > The thermal core restricts names of thermal zones to under 20
> > characters. Fix the names
On 25/04/2019 08:31, Amit Kucheria wrote:
> [PATCH 3/3] arm64: dts: msm8998: thermal: Restrict thermal zone name length
> to under 20
>
> The thermal core restricts names of thermal zones to under 20
> characters. Fix the names for a couple of msm8998 thermal zones.
>
> Signed-off-by: Amit Kuch
On 25/04/2019 08:31, Amit Kucheria wrote:
> Marc, can you please test these 3 patches on top of my original series?
Roger that.
# dmesg | grep thermal
/* NOTHING */
# for F in $(find /sys/class/thermal/thermal_zone?/
/sys/class/thermal/thermal_zone??/ -type f); do echo $F; cat $F; done
/sys/cl
On 25/04/2019 08:31, Amit Kucheria wrote:
> Andy, patches 1 and 2 fix problems that already exist upstream. They
> were not introduced by my series.
On IRC, you wrote: "can you send me the same output against mainline
(or linux-next) w/o my patches applied?"
$ git show 58ad5ab73152
commit 58ad5a
Marc, can you please test these 3 patches on top of my original series?
Andy, patches 1 and 2 fix problems that already exist upstream. They
were not introduced by my series.
Patch 3 fixes an issue with my series where the name of the thermal
zone was too long. You can choose to fold it into the p
On 23/04/2019 15:10, Marc Gonzalez wrote:
> 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?
I have synced up with today's linux-next.
# d
On Tue, Apr 23, 2019 at 06:26:40PM +0530, 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:
> > >>
> > >
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
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 us
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 r
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 t
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 temperatur
12 matches
Mail list logo
