Hi John, On Tue, Dec 08, 2015 at 01:29:22PM -0800, John Stultz wrote: > This patch adds a basic driver to allow for commands like > "reboot bootloader" and "reboot recovery" to communicate this > reboot-reason to the bootloader. > > This is commonly done on Android devices, in order to reboot > the device into fastboot or recovery mode. It also supports > custom OEM specific commands, via "reboot oem-<value>". > > This driver pulls the phys memory address from DT as well as > the magic reason values that are written to the address for > each mode. > > For an example, this patch also adds the DT support for > the nexus7 device via its dts (which is not yet upstream). > > Thoughts and feedback would be appreciated! I wonder if 'reason' is the correct word. This driver says nothing about the reason why we reboot, but more what we should do next. Maybe something like purpose, scope or intention is more appropriate? Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
