17c82e206d
Many devices may want to request a bunch of resets and control them. So it's better to manage them as an array. Add APIs to _get() an array of reset_control, reusing the _assert(), _deassert(), and _reset() APIs for single reset controls. Since reset controls already may control multiple reset lines with a single hardware bit, from the user perspective, reset control arrays are not at all different from single reset controls. Note that these APIs don't guarantee that the reset lines managed in the array are handled in any particular order. Cc: Felipe Balbi <balbi@kernel.org> Cc: Jon Hunter <jonathanh@nvidia.com> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org> [p.zabel@pengutronix.de: changed API to hide reset control arrays behind struct reset_control] Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> |
||
---|---|---|
.. | ||
hisilicon | ||
sti | ||
tegra | ||
core.c | ||
Kconfig | ||
Makefile | ||
reset-a10sr.c | ||
reset-ath79.c | ||
reset-berlin.c | ||
reset-gemini.c | ||
reset-imx7.c | ||
reset-lpc18xx.c | ||
reset-meson.c | ||
reset-oxnas.c | ||
reset-pistachio.c | ||
reset-socfpga.c | ||
reset-stm32.c | ||
reset-sunxi.c | ||
reset-ti-sci.c | ||
reset-ti-syscon.c | ||
reset-uniphier.c | ||
reset-zx2967.c | ||
reset-zynq.c |