diff options
| author | Stephen Warren <swarren@nvidia.com> | 2016-06-17 09:43:58 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2016-06-19 17:05:55 -0600 |
| commit | 89c1e2da78f82a09685006291ce8bb44f635fa25 (patch) | |
| tree | 4962e19a65e7cf8caf997ee92ec16030dead512a /doc/README.mxc_hab | |
| parent | 0f67e2395be44db2c1bef17b6ada2e46221908ed (diff) | |
| download | u-boot-imx-89c1e2da78f82a09685006291ce8bb44f635fa25.zip u-boot-imx-89c1e2da78f82a09685006291ce8bb44f635fa25.tar.gz u-boot-imx-89c1e2da78f82a09685006291ce8bb44f635fa25.tar.bz2 | |
Add a reset driver framework/uclass
A reset controller is a hardware module that controls reset signals that
affect other hardware modules or chips.
This patch defines a standard API that connects reset clients (i.e. the
drivers for devices affected by reset signals) to drivers for reset
controllers/providers. Initially, DT is the only supported method for
connecting the two.
The DT binding specification (reset.txt) was taken from Linux kernel
v4.5's Documentation/devicetree/bindings/reset/reset.txt.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/README.mxc_hab')
0 files changed, 0 insertions, 0 deletions