diff options
| author | Bjorn Andersson <bjorn.andersson@linaro.org> | 2017-01-22 22:17:48 +0100 |
|---|---|---|
| committer | Kishon Vijay Abraham I <kishon@ti.com> | 2017-01-27 08:36:52 +0100 |
| commit | 96c163f108ef7c0102ff71a543f5d5f2ad5c60a7 (patch) | |
| tree | 3fa73fc166d6545aee0163e781fd2b037d2a1aaf /drivers/phy/phy-qcom-ufs.c | |
| parent | phy: qcom-ufs: Correct usage of regulator_get() (diff) | |
| download | linux-96c163f108ef7c0102ff71a543f5d5f2ad5c60a7.tar.xz linux-96c163f108ef7c0102ff71a543f5d5f2ad5c60a7.zip | |
phy: qcom-ufs: Remove -always-on property
The fact that a regulator is always-on is a property of the regulator,
not a specific consumer. Implementing this in the driver leads to a
system behaviour that is dependent on if the Qualcomm UFS PHY was ever
(partially) probed.
If the specific regulator should be always on in a particular device,
mark it so by specifying "regulator-always-on" in the regulator node.
Reviewed-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Reviewed-by: Subhash Jadavani <subhashj@codeaurora.org>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Diffstat (limited to 'drivers/phy/phy-qcom-ufs.c')
| -rw-r--r-- | drivers/phy/phy-qcom-ufs.c | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/drivers/phy/phy-qcom-ufs.c b/drivers/phy/phy-qcom-ufs.c index bbd317158084..c145fa6e824c 100644 --- a/drivers/phy/phy-qcom-ufs.c +++ b/drivers/phy/phy-qcom-ufs.c @@ -242,9 +242,6 @@ static int ufs_qcom_phy_init_vreg(struct device *dev, } err = 0; } - snprintf(prop_name, MAX_PROP_NAME, "%s-always-on", name); - vreg->is_always_on = of_property_read_bool(dev->of_node, - prop_name); } if (!strcmp(name, "vdda-pll")) { @@ -402,7 +399,7 @@ static int ufs_qcom_phy_disable_vreg(struct device *dev, { int ret = 0; - if (!vreg || !vreg->enabled || vreg->is_always_on) + if (!vreg || !vreg->enabled) goto out; ret = regulator_disable(vreg->reg); |