On Thu, Nov 18, 2010 at 01:45:29PM -0500, Ira W. Snyder wrote: [ ... ] > > > > A more common and chip independent solution to such scenarios would be to have a dedicated register > > in the system to log reboot reasons. This can be anything - nvram, a chip register, or something else. > > I don't think it is a good idea to make assumptions about reboot reasons based on the behavior > > of one specific chip. > > > > I can offer some insight on how I'd handle this, if the LTC4215 EN bit > was the method used to detect SW reset on my board. > > I use the U-Boot bootloader to load Linux. I have no need to access the > chip while the bootloader is running. It would be very easy to have the > bootloader read the value and cache it somewhere. Some possibilities > include the U-Boot environment, or an unused register (I use a mpc83xx > chip, which has two of these). > Even then it might be simpler to just store the reset reason in one of the unused registers and access it after the reboot. This assumes, of course, that the registers retain their value after a reboot and have a well defined content after poweron. Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
