summaryrefslogtreecommitdiffstats
path: root/drivers/reset/Kconfig
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2012-10-23 23:45:56 +0200
committerPhilipp Zabel <p.zabel@pengutronix.de>2013-04-12 10:25:25 +0200
commit4e11f848c65b1c87782cb232a6e3b47a9d4c1f98 (patch)
tree907e6b4a3dccf87cc98655775fb6ee613138b97b /drivers/reset/Kconfig
parentLinux 3.9-rc4 (diff)
downloadlinux-4e11f848c65b1c87782cb232a6e3b47a9d4c1f98.tar.xz
linux-4e11f848c65b1c87782cb232a6e3b47a9d4c1f98.zip
dt: describe base reset signal binding
This binding is intended to represent the hardware reset signals present internally in most IC (SoC, FPGA, ...) designs. It consists of a binding for a reset controller device (provider), and a pair of properties, "resets" and "reset-names", to link a device node (consumer) to its reset controller via phandle, similarly to the clock and interrupt bindings. The reset controller has all information necessary to reset the consumer device. That could be provided via device tree, or it could be implemented in hardware. The aim is to enable device drivers to request a framework API to issue a reset simply by providing their struct device pointer as the most common case. Signed-off-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> Reviewed-by: Shawn Guo <shawn.guo@linaro.org> Reviewed-by: Marek Vasut <marex@denx.de> Reviewed-by: Pavel Machek <pavel@ucw.cz> Acked-by: Rob Herring <rob.herring@calxeda.com>
Diffstat (limited to 'drivers/reset/Kconfig')
0 files changed, 0 insertions, 0 deletions