summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/ufs
diff options
context:
space:
mode:
authorEvan Green <evgreen@chromium.org>2019-03-21 20:17:54 +0300
committerKishon Vijay Abraham I <kishon@ti.com>2019-04-17 11:42:53 +0300
commit95cee0b4e30a09a411a17e9a3bc6b72ed92063da (patch)
tree81024ef1bbd219b16f5f7aaff211b16c4b1d7cb8 /Documentation/devicetree/bindings/ufs
parent8de4acd397ab96bf3487c6a765fd2b76e2863909 (diff)
downloadlinux-95cee0b4e30a09a411a17e9a3bc6b72ed92063da.tar.xz
dt-bindings: phy-qcom-qmp: Add UFS PHY reset
Add a required reset to the SDM845 UFS phy to express the PHY reset bit inside the UFS controller register space. Before this change, this reset was not expressed in the DT, and the driver utilized two different callbacks (phy_init and phy_poweron) to implement a two-phase initialization procedure that involved deasserting this reset between init and poweron. This abused the two callbacks and diluted their purpose. That scheme does not work as regulators cannot be turned off in phy_poweroff because they were turned on in init, rather than poweron. The net result is that regulators are left on in suspend that shouldn't be. This new scheme gives the UFS reset to the PHY, so that it can fully initialize itself in a single callback. We can then turn regulators on during poweron and off during poweroff. Signed-off-by: Evan Green <evgreen@chromium.org> Reviewed-by: Rob Herring <robh@kernel.org> Reviewed-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Diffstat (limited to 'Documentation/devicetree/bindings/ufs')
0 files changed, 0 insertions, 0 deletions