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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 21 Dec 2017 15:13:41 -0800
From:   Stephen Boyd <>
To:     Gregory CLEMENT <>
Cc:     Mike Turquette <>,,,
        Jason Cooper <>,
        Andrew Lunn <>,
        Sebastian Hesselbarth <>,
        Thomas Petazzoni <>,,
        Antoine Tenart <>,
        Miquèl Raynal 
        Nadav Haklai <>,
        Victor Gu <>, Marcin Wojtas <>,
        Wilson Ding <>,
        Hua Jing <>,
        Neta Zur Hershkovits <>
Subject: Re: [PATCH 0/3] Add DVFS support on CPU clock for Armada 37xx

On 11/30, Gregory CLEMENT wrote:
> Hi,
> This small series is needed to use DVFS on Armada 37xx. When DVFS is
> enabled the CPU clock setting is done using an other set of registers
> from the North Bridge Power Management block.
> The series adds the possibility to modify the CPU frequency using the
> associate load level matching the target frequency. However
> configuring the frequencies for each load is done by the cpufreq
> driver submitted in a separate series.
> Obviously having both series (cpufreq and clk) is needed to support
> DVFS on Armada 37xx, but there is no dependencies between the series
> (for building or at runtime).

Are you relying on the clk API returning an error to detect if
DVFS is present or not? Just curious why that part of the code
was there.

Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

Powered by blists - more mailing lists