Simon Glass f9917454d5 dm: Add a system reset uclass ... It is common for system reset to be available at multiple levels in modern hardware. For example, an SoC may provide a reset option, and a board may provide its own reset for reasons of security or thoroughness. It is useful to be able to model this hardware without hard-coding the behaviour in the SoC or board. Also there is a distinction sometimes between resetting just the CPU (leaving GPIO state alone) and resetting all the PMICs, just cutting power. To achieve this, add a simple system reset uclass. It allows multiple devices to provide reset functionality and provides a way to walk through them, requesting a particular reset type until is it provided. Signed-off-by: Simon Glass <sjg@chromium.org>		2015-07-21 17:39:29 -06:00
..
platform_data	dm: sh: serial: Add support driver model	2015-02-12 15:17:17 -07:00
device-internal.h	dm: core: Convert driver_bind() to use const	2015-04-18 11:11:19 -06:00
device.h	dm: core: Correct device_get_child_by_of_offset() parameter	2015-07-21 17:39:23 -06:00
lists.h	dm: core: Add a function to bind a driver for a device tree node	2015-04-29 21:02:32 -06:00
platdata.h	dm: core: Allow a list of devices to be declared in one step	2014-10-22 10:36:54 -06:00
root.h	dm: Add dm_scan_other() to locate board-specific devices	2014-07-23 14:08:37 +01:00
test.h	test: dm: Move the dm tests over to the ut command	2015-05-21 09:16:17 -04:00
uclass-id.h	dm: Add a system reset uclass	2015-07-21 17:39:29 -06:00
uclass-internal.h	dm: core: Remove unbind operations when not required	2015-04-23 09:05:52 -06:00
uclass.h	dm: core: precise comments for get/find device by name	2015-04-22 11:03:16 -06:00
util.h	dm: Move the tree/uclass dump code into its own file	2015-07-21 17:39:22 -06:00