Andrew,
On Tue, Jul 16, 2013 at 04:04:15PM +0200, Andrew Lunn wrote:
On Mon, Jul 15, 2013 at 08:32:38PM -0300, Ezequiel Garcia wrote:
quoted
Instead of accessing the RSTOUT register directly, this commit
adds a platform memory resource to map this register into the driver.
Have you looked at:
arch/arm/mach-mvebu/system-controller.c
Mmm... I saw the use of the RSTOUT register in kirkwood_restart()
but wasn't sure who should be the real 'owner' of this register.
It is also using this register. Are we going to have a similar problem
as the TIMER_CTRL register, which you refactered in an earlier patch?
Probably.
"marvell,orion-system-controller" is not actually used yet, but once
kirkwood moves into mach-mvebu, it will start using it.
I guess so. We should take that into account *now*. Let me think about
it and see if I can have something sane for v2.
Thanks!
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com