Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> writes: > Thara Gopinath <thara@xxxxxx> writes: > >> From: thara gopinath <thara@xxxxxx> >> >> This patch series introduces smartreflex and voltage driver support >> for OMAP3430 and OMAP3630. SmartReflex modules do adaptive voltage >> control for real-time voltage adjustments. > > [...] > >> This patch series is based against origin/pm-core branch off >> Kevin's pm tree which in turn is based off lo-master. >> This series will apply against lo-master also but will >> break compilation due to lack of opp framework support >> on lo-master. >> >> This patch series has been tested on OMAP3430 SDP with the extra five patches >> from origin/cpufreq branch off Kevin's pm tree applied. This series >> has been tested with with omap3_defconfig with the following >> menuconfig options enabled. >> System type -> TI OMAP Implementations -> Smartreflex Support >> System type -> TI OMAP Implementations -> >> Class 3 mode of Smartreflex Implementation > > Using the same baseline as you mention above (pm-core + pm-opp), I > applied this series (and the OMAP4 series) and tested on 34xx/n900 and > 36xx/Zoom3 using omap2plus_defconfig and it booted ok. (I also patched > the n900 board file to call sr_class3_init(), which you should include > as part of the series too.) > > I then did some experiments, including updating the pm-sr branch to be > this latest series and testing with omap3_pm_defconfig. With that, I > notcied that within a few seconds of reaching the shell, the system > rebooted. > > I tracked this down to the fact that CONFIG_OMAP_WATCHDOG was not > enabled in omap3_pm_defconfig. Enabling the watchdog, and it no longer > reboots. /me confused > > Using just the pm-sr branch by itself and omap2plus_defconfig, even with > the watchdog disabled, it doesn't reboot. > > Do you have any ideas what else might be causing this reboot when using > the PM branch + omap3_pm_defconfig? So, I did a little more digging, and this has nothing to do with your series. It has to do with the watchdog hwmod series, which due to the new hwmods, resets the watchdog IP. So, if a watchdog driver isn't enabled, the watchdog will fire, and cause a reboot. Kevin -- 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
