PM / clock_ops: provide default runtime ops and cleanup users
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 5 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 5 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] PM / clock_ops: provide default runtime ops and cleanup users
Quoted 34 lines · Simon Horman
Quoted 21 lines · Geert Uytterhoeven
Quoted 20 lines · Rafael J. Wysocki
Quoted 18 lines · Rajendra Nayak
Most users of PM clocks do the exact same thing in runtime callbacks. Provide default callbacks and cleanup the existing users (keystone/davinci /omap1/sh)
Rajendra Nayak (5):
PM /clock_ops: Provide default runtime ops to users
arm: keystone: remove boilerplate code and useUSE_PM_CLK_RUNTIME_OPS
arm: omap1: remove boilerplate code and useUSE_PM_CLK_RUNTIME_OPS
arm: davinci: remove boilerplate code and useUSE_PM_CLK_RUNTIME_OPS
drivers: sh: remove boilerplate code and useUSE_PM_CLK_RUNTIME_OPSarch/arm/mach-davinci/pm_domain.c | 32 +------------------------- arch/arm/mach-keystone/pm_domain.c | 33 +------------------------- arch/arm/mach-omap1/pm_bus.c | 37 ++---------------------------- drivers/base/power/clock_ops.c | 38 ++++++++++++++++++++++++++++++ drivers/sh/pm_runtime.c | 47 ++------------------------------------ include/linux/pm_clock.h | 10 ++++++++ 6 files changed, 54 insertions(+), 143 deletions(-)Quoted 7 lines
Quoted 2 lines
It is not particularly clear to me who is supposed to apply this series, but I can do that if people don't have problems with that.
All later patches depend on the first patch.
For shmobile, Simon has queued up changes for
drivers/sh/pm_runtime.c, but I think they don't conflict with this series.Yes, that is the case. I have some patches (from Geert) queued up for v4.1. I have confirmed that they do not conflict with the shmobile (last) patch if this series.
Quoted 5 lines
<details>
The patches are in the sh-drivers-for-v4.1 branch of my renesas tree; I rebased them yesterday; they should hit next today if there is a next today; I plan to send a pull request to Linus in the not to distant future; and I envisage they should end up in v4.1-rc2 or rc3.
The above mentioned changes were tagged as renesas-sh-drivers-for-v4.1 in my renesas tree; were merged into in Linus's tree yesterday; and should thus be included in v4.1-rc2.
I do not have any other changes to drivers/sh/pm_runtime.c pending at this time.
Quoted 25 lines
</details>
Quoted 2 lines · santosh shilimkar
Quoted 1 line · Rafael J. Wysocki
On Thursday, April 23, 2015 02:03:08 PM Rajendra Nayak wrote:
[snip]
Quoted 9 lines
Quoted 4 lines
It is not particularly clear to me who is supposed to apply this series, but I can do that if people don't have problems with that.
I am fine by that given dependency with first patch. Another way is, you pick up the first patch and give us an immutable branch.
Either way is fine by me.
Likewise.
Here is an ack for the shmobile (last) patch if you decide to take it through your tree.
Acked-by Simon Horman <[email protected]>