linux-kernel - [PATCH 00/12] PM / devfreq: Use OPP interface to handle the frequency

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-next>] [day] [month] [year] [list]

Date:   Thu, 24 Aug 2017 10:42:47 +0900
From:   Chanwoo Choi <cw00.choi@...sung.com>
To:     myungjoo.ham@...sung.com, kyungmin.park@...sung.com,
        cw00.choi@...sung.com
Cc:     rafael.j.wysocki@...el.com, chanwoo@...nel.org,
        inki.dae@...sung.com, linux-kernel@...r.kernel.org,
        linux-pm@...r.kernel.org
Subject: [PATCH 00/12] PM / devfreq: Use OPP interface to handle the
 frequency

These patches makes the devfreq to use the OPP interface as a mandatory
and fix the bug, clean-up codes.
- patch 1/2 fix the bug.
- patch 3 refactors the private code.
- patch 4~12 are related to the OPP interfaces 

The commit a76caf55e5b3 ("thermal: Add devfreq cooling") provides
the devfreq cooling device by using the OPP interface such as
dev_pm_opp_disable() and dev_pm_opp_enable(). It means that
the OPP interface is able to change the available status of the frequency.

Firstly, the existing devfreq doesn't use the OPP interface when showing
the minimum and maximum frequency through the following sysfs nodes:
It shows the wrong frequency value because min_freq/max_freq don't
consider the frequency status by handling OPP interface. So, these
patches fix this issue.
- /sys/class/devfreq/devfreq.X/min_freq
- /sys/class/devfreq/devfreq.X/max_freq

Second, the 'available_frequencies' should show the all supported frequencis
even if the specific frequency is not available. It doesn't matter whether
frequneyc is available or not. Because the role of 'available_frequencies'
shows the all frequencies. Also, these patches fix this issue.
- /sys/class/devfreq/devfreq.X/available_frequencies

Lastly, the devfreq uses the OPP interface as a mandatory method
and so the devfreq has to support the OPP notifier in order to
catch the OPP events. So, patch12 adds the new opp_notifier_cb()
function pointer in the struct devfreq_dev_profile. The user can
add the their own callback function to receive the OPP events.

Also, the devfreq provides the default OPP notifeir callback
in order to remake the frequency table when OPP events happen.
- default_opp_notifier_cb()

Chanwoo Choi (12):
  PM / devfreq: Fix memory leak when fail to register device
  PM / devfreq: Fix locking range for making the frequency table
  PM / devfreq: Move private devfreq_update_stats() into devfreq
  PM / devfreq: Add dependency on PM_OPP
  PM / devfreq: Set min/max_freq when adding the devfreq device
  PM / devfreq: Check the entered min/max_freq is supported or not
  Revert "PM / devfreq: Add show_one macro to delete the duplicate code"
  PM / devfreq: Show the available min/max frequency through sysfs node
  PM / devfreq: Show whole available frequencies
  PM / devfreq: Remove 'devfreq' prefix from helper function
  PM / devfreq: Remove exported opp_notifier function
  PM / devfreq: Add opp_notifier_cb() function pointer to support OPP
    notifier

 drivers/devfreq/Kconfig      |   1 +
 drivers/devfreq/devfreq.c    | 286 +++++++++++++++++++++++++------------------
 drivers/devfreq/exynos-bus.c |   7 --
 drivers/devfreq/governor.h   |   4 +
 drivers/devfreq/rk3399_dmc.c |   1 -
 include/linux/devfreq.h      |  56 ++-------
 6 files changed, 181 insertions(+), 174 deletions(-)

-- 
1.9.1