From: Dave Gerlach <d-gerlach@...> commit 953a0f18337406ab041252ce5a62db5d173bee5f upstream. Add the device tree bindings document for the TI CPUFreq/OPP driver on AM33xx, AM43xx, DRA7xx, and AM57x

So I tried just backporting the ti-cpufreq driver. However as the am33xx OPP table wasn't completely converted to the v2 format, missing the clock-latency-ns property, it is unusable in this standalon

Hi, <masashi.kudo@...> wrote: I might not make it, so here are updates from me for this week: Two new issues: - CVE-2020-11935 (aufs, not applicable to mainline) - CVE-2020-14314 (ext4 re

From: Viresh Kumar <viresh.kumar@...> commit 2c2709dc6921c5d246b686521f932c73a20f428f upstream. Stephen pointed out recently, that few structures always confuse him as they aren't named properl

From: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@...> commit c5c2a97b3ac7d1ec19e7cff9e38caca6afefc3de upstream. This commit fixes a rare but possible case when the clk rate is updated without

From: Viresh Kumar <viresh.kumar@...> commit 21f8a99ce61b2d4b74bd425a5bf7e9efbe162788 upstream. Regulators are optional for devices using OPPs and the OPP core shouldn't be printing any errors

From: Viresh Kumar <viresh.kumar@...> commit b318556479cc923970a79d6c2311138581c0db83 upstream. The comment in file header doesn't hold true anymore, drop it. Signed-off-by: Viresh Kumar <vires

From: Viresh Kumar <viresh.kumar@...> commit df2c8ec28e73d47392b8cb24828c15c54819da41 upstream. Its already done by core and we don't need to get it anymore. And so, we don't need to get of nod

From: Viresh Kumar <viresh.kumar@...> commit a5da64477ee79efa748df256928ec8840a2a7986 upstream. Some comments were just copy/pasted from other sections and don't match to the routines they were

From: Viresh Kumar <viresh.kumar@...> commit 0c717d0f9cb46259dce5272705adce64a2d646d9 upstream. We are currently required to do two checks for regulator pointer: IS_ERR() and IS_NULL(). And mul

From: Jon Hunter <jonathanh@...> commit 78ecc56247f0ec2bc0cf6f2f2af69e98d99767bc upstream. Commit 7d34d56ef334 (PM / OPP: Disable OPPs that aren't supported by the regulator) causes a crash to

From: Viresh Kumar <viresh.kumar@...> commit dd02a3d920083b6cb0ee4f0eaf2c599b740bf5fe upstream. OPP layer manages it now and cpufreq-dt driver doesn't need it. But, we still need to check for a

From: Viresh Kumar <viresh.kumar@...> commit 896d6a4c0f41a93809b83f9e58aad73874a89d99 upstream. We have the device structure available now, lets use it for better print messages. Signed-off-by:

From: Viresh Kumar <viresh.kumar@...> commit 78c3ba5df96c875b1668e1cd3ee0a69e62454f32 upstream. OPP core supports frequency/voltage changes based on the target frequency now, use that instead o

From: Viresh Kumar <viresh.kumar@...> commit 457e99e60a8f5a40b7da204c0bfc8a86ad2161b9 upstream. That's the real purpose of this field, i.e. to take special care of old OPP V1 bindings. Lets nam

From: Viresh Kumar <viresh.kumar@...> commit 755b888ff098c9f762717a9fbda7e05b16619069 upstream. OPP layer has all the information now to calculate transition latency (clock_latency + voltage_la

From: Viresh Kumar <viresh.kumar@...> commit 391d9aef8145204e0a5d67be3bd1fc45c5396dae upstream. "clock-latency" is handled by OPP layer for all bindings and so there is no need to make special

From: Viresh Kumar <viresh.kumar@...> commit 050794aaebbb9f2c2c50b340b6998273e7c64189 upstream. OPP core can handle the regulators by itself, and but it needs to know the name of the regulator

From: Viresh Kumar <viresh.kumar@...> commit 6def6ea75e6dea45f01a16ae3cfb5b5ce48dd5e9 upstream. The core already have a valid regulator set for the device opp and the unsupported OPPs are alrea

From: Viresh Kumar <viresh.kumar@...> commit d54974c2513f487e9e70fbdc79c5da51c53e23da upstream. OPP core has got almost everything now to manage device's OPP transitions, the only thing left is