lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 30 Aug 2018 10:55:17 +0530
From:   Amit Kucheria <>
To:     Daniel Lezcano <>
Cc:     Linux Kernel Mailing List <>,
        Rajendra Nayak <>,
        linux-arm-msm <>,
        Bjorn Andersson <>,
        Andy Gross <>,
        Doug Anderson <>,,
        Eduardo Valentin <>,
        David Brown <>,
        Rob Herring <>,
        Mark Rutland <>,
        Catalin Marinas <>,
        Will Deacon <>,
        "open list:ARM/QUALCOMM SUPPORT" <>,
        DTML <>,
        Lists LAKML <>
Subject: Re: [PATCH v1] arm64: dts: sdm845: enable tsens thermal zones

On Wed, Aug 29, 2018 at 3:09 PM Daniel Lezcano
<> wrote:
> On 18/07/2018 09:49, Amit Kucheria wrote:
> > One thermal zone per cpu is defined
> The thermal zones are very close, especially when the CPUs belong to the
> same 'cluster'. Very likely the temperature will propagate from one core
> to another core, so when one core reaches the trip0, there is good
> chance the other cores will be close and cross the trip0 threshold too.

Agreed. Once we have all the thermal and cpufreq bits in place, I'd
like to examine optimisations such as a virtual sensor, using the
coefficients to add weights, etc.

> Having multiple thermal zones, one per CPU, may trigger an interrupts
> storm with the passive polling timer delay.

I'm working on irq support for tsens that should alleviate that.

> Does this board have a cooling device per CPU also ?

As Matthias mentioned, DVFS is per cluster (4 cpus to a cluster).

Powered by blists - more mailing lists