Re: [PATCH 3/4] phy: qcom-ufs: Remove -always-on property

2017-01-21 Thread Rob Herring
On Thu, Jan 19, 2017 at 02:47:38AM -0800, Bjorn Andersson wrote: > 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) prob

Re: [PATCH 3/4] phy: qcom-ufs: Remove -always-on property

2017-01-20 Thread Subhash Jadavani
On 2017-01-19 02:47, Bjorn Andersson wrote: 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 regula

Re: [PATCH 3/4] phy: qcom-ufs: Remove -always-on property

2017-01-19 Thread Vivek Gautam
On Thu, Jan 19, 2017 at 4:17 PM, Bjorn Andersson wrote: > 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. > >

[PATCH 3/4] phy: qcom-ufs: Remove -always-on property

2017-01-19 Thread Bjorn Andersson
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