2020-09-29 09:00:40

by Chanwoo Choi

[permalink] [raw]
Subject: [GIT PULL] devfreq next for v5.10

Dear Rafael,

This is devfreq-next pull request for v5.10-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.10

Best Regards,
Chanwoo Choi


The following changes since commit a1b8638ba1320e6684aa98233c15255eb803fac7:

Linux 5.9-rc7 (2020-09-27 14:38:10 -0700)

are available in the Git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-next-for-5.10

for you to fetch changes up to d353d1202b89ab039acd079cd97f7646058ebe11:

PM / devfreq: tegra30: Improve initial hardware resetting (2020-09-29 17:50:10 +0900)

----------------------------------------------------------------

Detailed description for this pull request:
1. Update devfreq core
- Until now, devfreq and devfreq-event framework defines the fixed 'devfreq'
and 'devfreq-event' property to get the devfreq/devfreq-event phandle. But,
these property name are not expressing the h/w. So, deprecate the fixed
property name of both 'devfreq' and 'devfreq-event'. But, in order to keep
the backward compatibility of devicetree, doesn't change the property name
on devfreq device drivers and devicetree.

2. Update devfreq driver
- Replace reset_control_(assert|dessert) fucntions with reset_control_reset()
for reseting the h/w during probe on tegra30-devfreq.c.

----------------------------------------------------------------

Chanwoo Choi (2):
PM / devfreq: Change prototype of devfreq_get_devfreq_by_phandle function
PM / devfreq: event: Change prototype of devfreq_event_get_edev_by_phandle function

Dmitry Osipenko (1):
PM / devfreq: tegra30: Improve initial hardware resetting

Leonard Crestez (1):
PM / devfreq: Add devfreq_get_devfreq_by_node function

drivers/devfreq/devfreq-event.c | 14 ++++----
drivers/devfreq/devfreq.c | 57 ++++++++++++++++++++++++---------
drivers/devfreq/exynos-bus.c | 7 ++--
drivers/devfreq/rk3399_dmc.c | 2 +-
drivers/devfreq/tegra30-devfreq.c | 8 +++--
drivers/memory/samsung/exynos5422-dmc.c | 6 ++--
include/linux/devfreq-event.h | 14 +++++---
include/linux/devfreq.h | 11 +++++--
8 files changed, 83 insertions(+), 36 deletions(-)


2020-09-30 16:00:34

by Rafael J. Wysocki

[permalink] [raw]
Subject: Re: [GIT PULL] devfreq next for v5.10

On Tue, Sep 29, 2020 at 10:56 AM Chanwoo Choi <[email protected]> wrote:
>
> Dear Rafael,
>
> This is devfreq-next pull request for v5.10-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.10

Pulled, thanks!

2020-10-06 07:58:39

by Chanwoo Choi

[permalink] [raw]
Subject: Re: [GIT PULL] devfreq next for v5.10

Dear Rafael,

On 10/1/20 12:56 AM, Rafael J. Wysocki wrote:
> On Tue, Sep 29, 2020 at 10:56 AM Chanwoo Choi <[email protected]> wrote:
>>
>> Dear Rafael,
>>
>> This is devfreq-next pull request for v5.10-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.10
>
> Pulled, thanks!

Thanks for pulled the request. But, I tried to check on linux-pm.git,
I cannot find the pull request of devfreq patches for v5.10-rc1.

Best Regards,
Chanwoo Choi

2020-10-06 10:29:49

by Rafael J. Wysocki

[permalink] [raw]
Subject: Re: [GIT PULL] devfreq next for v5.10

On Tue, Oct 6, 2020 at 9:57 AM Chanwoo Choi <[email protected]> wrote:
>
> Dear Rafael,
>
> On 10/1/20 12:56 AM, Rafael J. Wysocki wrote:
> > On Tue, Sep 29, 2020 at 10:56 AM Chanwoo Choi <[email protected]> wrote:
> >>
> >> Dear Rafael,
> >>
> >> This is devfreq-next pull request for v5.10-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.10
> >
> > Pulled, thanks!
>
> Thanks for pulled the request. But, I tried to check on linux-pm.git,
> I cannot find the pull request of devfreq patches for v5.10-rc1.

That's because they were not merged back into my linux-next branch and
they should be there now.

Thanks!