linux-kernel - Re: [GIT PULL] devfreq next for v5.5

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJZ5v0g0zN8bATL6LsVJDq_5tD_m+Uc4LYmeY-8QJHQWMvTRyw@mail.gmail.com>
Date:   Thu, 7 Nov 2019 13:57:17 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Chanwoo Choi <cw00.choi@...sung.com>
Cc:     "Rafael J. Wysocki <rjw@...ysocki.net>" <rjw@...ysocki.net>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
        "Chanwoo Choi (samsung.com)" <chanwoo@...nel.org>,
        함명주 <myungjoo.ham@...sung.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] devfreq next for v5.5

On Thu, Nov 7, 2019 at 4:57 AM Chanwoo Choi <cw00.choi@...sung.com> wrote:
>
> Dear Rafael,
>
> This is devfreq-next pull request for v5.5-rc1. I add detailed description of
> this pull request on the following tag. Please pull devfreq with following updates.
> - tag name : devfreq-next-for-5.5
>
>
> When pull the this pull request to linux-pm, auto-merging will happen.
> Because of the change of the devfreq git information on patch[1] and
> patch[2] add the additional information of exynos_ppmu.h.
> But, when I tested it, the auto merging was completed without problem.
> If the problem happen, I'll resend the pull request rebased on
> the top of 'linux-next' branch instead of Linux 5.4-rc6.
>
> [1] MAINTAINERS: Update myself as maintainer for DEVFREQ subsystem support
> - https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=c389ec67b7f8e028438643c4af4bbff550192187
>
> [2] include: dt-bindings: add Performance Monitoring Unit for Exynos
> - https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git/commit/?h=devfreq-next&id=fcbd8037f7df694aa7bfb7ce82c0c7f5e53e7b7b
>
> Best Regards,
> Chanwoo Choi
>
>
> The following changes since commit a99d8080aaf358d5d23581244e5da23b35e340b9:
>
>   Linux 5.4-rc6 (2019-11-03 14:07:26 -0800)
>
> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-next-for-5.5
>
> for you to fetch changes up to fee22854c0273569836de2039d9c432ea4df2cfc:
>
>   PM / devfreq: tegra30: Tune up MCCPU boost-down coefficient (2019-11-06 12:04:01 +0900)
>
> ----------------------------------------------------------------
> Update devfreq for 5.5
>
> Detailed description for this pull request:
> 1. Update devfreq core
> - Check NULL governor in available_governors_show sysfs in order to prevent
>   showing the wrong governor information.
> - Fix the race condition between devfreq_update_status() and trans_stat_show()
> - Add new 'interrupt-driven' flag for devfreq goveror. Each devfreq driver can
>   add the their own governor (NIVIDIA Tegra30 ACTMON governor) which is interrupt-driven
>   governor. It needs to use the following sysfs interface to get the new polling
>   interval in order to change the NVIDIA Tegra30 hardware's polling interval.
>   : /sys/class/devfreq/devfreqX/polling_interval
>   So, if 'interrupt-driven' flag of devfreq governor is 1, the devfreq governor
>   is able to use the 'polling_interval' sysfs interface to get the new polling
>   interval value. But, the devfreq core doesn't schedule out the polling work
>   for this governor like NVIDIA Tegra30 ACTMON governor.
>
> 2. Update devfreq driver
> - For exynos-bus.c, remove unused property from dt-binding documentation
> - For tegra30-devfreq.c, update the internal behavior like fixing the overflow
>   integer issue and clean-up code.
>
> 3. Update devfreq-event driver
> - For exynos-ppmu.c, add exynos_ppmu.h dt-binding file for 'event-data-type' filed.
>   and update dt-binging documentation. Also,  Fix minor coding style.

Pulled, and thanks a lot for the nice description of the contents,
much appreciated!

Also it has merged for me cleanly.

Thanks!