On 24.05.2018 12:36, Rafael J. Wysocki wrote: > On Wednesday, May 23, 2018 11:30:39 AM CEST Dmitry Osipenko wrote: >> On 23.05.2018 08:58, Viresh Kumar wrote: >>> On 23-05-18, 00:14, Dmitry Osipenko wrote: >>>> Tegra20-cpufreq driver missed enabling the CPU clocks. This results in a >>>> clock-enable refcount disbalance on PLL_P <-> PLL_X reparent, causing >>>> PLL_X to get disabled while it shouldn't. Fix this by enabling the clocks >>>> on the driver probe. >>>> >>>> Signed-off-by: Dmitry Osipenko <digetx@xxxxxxxxx> >>>> --- >>>> >>>> CPUFreq maintainers, >>>> >>>> Please take into account that this patch is made on top of my recent >>>> series of patches [0] "Clean up Tegra20 cpufreq driver" that was fully >>>> reviewed, but seems not applied yet. Let me know if you prefer to re-spin >>>> the [0], including this patch into the series. >>>> >>>> [0] https://patchwork.ozlabs.org/project/linux-tegra/list/?series=45321 >>> >>> This is already picked by Rafael and is sitting in pm/bleeding-edge >>> branch. Should get merged into linux-next in a day or two. >> >> Neat, thank you for letting me know. > > It actually is there in my linux-next branch, but linux-next proper is not > taking new material this week AFAICS. I've found it in yours git repo, thank you. > You'll see this in linux-next on Monday, most probably. > Yes, I noticed that linux-next stopped updating for awhile. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
