Hi Paul,
On 6/11/2012 10:04 AM, Paul Walmsley wrote:
On Sun, 10 Jun 2012, Tony Lindgren wrote:
* Paul Walmsley <paul@xxxxxxxxx> [120608 06:33]:
I don't really have a huge problem with switching to a late reset,
but there are disadvantages to it.
I think the early reset actually has more disadvantages to it compared
to driver reset. We don't see any errors when things go wrong, and we
may even kill the only debug console in the reset process.
We are already doing what Benoit describes with clocks where we only
reset the unclaimed ones at late_initcall level, and that has proven
to work well.
The difference though between the clock and the IP block init is that
leaving the clocks on until later has no effect on system stability. The
chip simply consumes more energy.
But if the IP blocks are reset later, and the bootloader or previous OS
gets some register settings wrong, there's a greater risk of system
instability or unpredictable behavior during the boot process.
Mmm, I'm not convince by that. If we delay the PM init at the very last
time, at least after the modules are properly reset and init, I do not
think we will have more issues than today.
Regards,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
