[PATCH 0/5] ARM: shmobile: pm domain improvements and cleanups

[PATCH 0/5] ARM: shmobile: pm domain improvements and cleanups

[Geert Uytterhoeven]

	Hi Simon, Magnus,

This patch series improves and cleans up the initialization of power domains
and their devices on sh7372/mackerel and r8a7740/armadillo800eva.

Geert Uytterhoeven (5):
  ARM: shmobile: mackerel: Make domain_devices[] static __initdata
  ARM: shmobile: sh7372: Make domain_devices[] static __initdata
  ARM: shmobile: r8a7740: Use rmobile_add_devices_to_domains()
  ARM: shmobile: armadillo800eva legacy: Use
    rmobile_add_devices_to_domains()
  ARM: shmobile: r8a7740: Clean up pm domain table

 arch/arm/mach-shmobile/board-armadillo800eva.c |    8 ++++++--
 arch/arm/mach-shmobile/board-mackerel.c        |    2 +-
 arch/arm/mach-shmobile/pm-r8a7740.c            |   10 ++++-----
 arch/arm/mach-shmobile/setup-r8a7740.c         |   26 ++++++++++++++----------
 arch/arm/mach-shmobile/setup-sh7372.c          |    2 +-
 5 files changed, 27 insertions(+), 21 deletions(-)

-- 
1.7.9.5

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: [PATCH 0/5] ARM: shmobile: pm domain improvements and cleanups

[Simon Horman]

On Fri, Aug 29, 2014 at 03:26:17PM +0200, Geert Uytterhoeven wrote:
> 	Hi Simon, Magnus,
> 
> This patch series improves and cleans up the initialization of power domains
> and their devices on sh7372/mackerel and r8a7740/armadillo800eva.

Thanks, I have queued these up.

As I have (once again) received push-back from the ARM-SoC maintainers
relating to cleanups I will describe my reasoning for picking these up
below.

I have picked these up because they can be applied cleanly on
top of v3.17-rc1 and do not conflict with anything else that is
currently queued up for v3.18. As such I do not believe I need
to consider deferring them until v3.19.

If, on the other hand, they had conflicted with patches queued up
for v3.18 I would have been hesitant to pick them up and probably
would have asked you to defer them until v3.19. This is because
within a release cycle the ARM-SoC maintainers have a preference for
cleanups to come before other changes.

I hope the above makes sense and may help everyone to understand
a little more how I am handling cleanups in accordance with request
made by the ARM-SoC maintainers.