lists.openwall.net   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  linux-cve-announce  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:   Wed, 19 Aug 2020 10:33:10 +0300
From:   Tony Lindgren <tony@...mide.com>
To:     Adam Ford <aford173@...il.com>
Cc:     linux-omap@...r.kernel.org, aford@...conembedded.com,
        BenoƮt Cousson <bcousson@...libre.com>,
        Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3] ARM: dts: omap3: Add cpu trips and cooling map for
 omap34/36 families

* Adam Ford <aford173@...il.com> [200818 15:57]:
> Currently, OMAP3_THERMAL is disabled by default, so the bandgap sensor
> is unavailable, and enabling it will somewhat increase power consumption.
> However for boards which operate near their thermal limit, OMAP3_THERMAL
> can be enabled and monitored to keep the processor from either running
> too fast, or shutdown when it's deemed to be operating at an unsafe
> thermal limit at the expense of increased power consumption.
> 
> The OMAP3530, OMAP3630, and DM3730 all show thresholds of 90C and 105C
> depending on commercial or extended temperature ratings.
> 
> This patch expands the thermal information to include the limits of
> 80C for alert and 90C critical based on commercial temperature rating.
> It sets the coolings-cells for the 34xx and 36xx CPU's which will start
> to throttle back their maximum frequency when the bangap sensor reads
> above the alert temerature of 80C.

Thanks applying into omap-for-v5.10/dt.

Tony

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ