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  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:   Fri, 8 Feb 2019 16:01:33 +0530
From:   Viresh Kumar <>
To:     "Rafael J. Wysocki" <>
Cc:     Marek Szyprowski <>,
        Linux Kernel Mailing List <>,
        Linux PM <>,
        Linux Samsung SoC <>,
        "Rafael J . Wysocki" <>,
        Nishanth Menon <>, Stephen Boyd <>,
        Bartlomiej Zolnierkiewicz <>,
        Dave Gerlach <>,
        Wolfram Sang <>
Subject: Re: [PATCH 0/2] cpufreq/opp: rework regulator initialization

On 08-02-19, 11:22, Rafael J. Wysocki wrote:
> There are cpufreq driver suspend and resume callbacks, maybe use them?
> The driver could do the I2C transactions in its suspend/resume
> callbacks and do nothing in online/offline if those are part of
> system-wide suspend/resume.

These are per-policy things that we need to do, not sure if driver
suspend/resume is a good place for that. It is more for a case where
CPU 0-3 are in one policy and 4-7 in another. Now 1-7 are
hot-unplugged during system suspend and hotplugged later on. This is
more like complete removal/addition of devices instead of


Powered by blists - more mailing lists