From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751634AbdAUUn0 (ORCPT ); Sat, 21 Jan 2017 15:43:26 -0500 Received: from mail-ot0-f194.google.com ([74.125.82.194]:35420 "EHLO mail-ot0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751131AbdAUUnF (ORCPT ); Sat, 21 Jan 2017 15:43:05 -0500 Date: Sat, 21 Jan 2017 14:43:02 -0600 From: Rob Herring To: Bjorn Andersson Cc: Kishon Vijay Abraham I , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, Mark Rutland , devicetree@vger.kernel.org, Subhash Jadavani , Vivek Gautam Subject: Re: [PATCH 3/4] phy: qcom-ufs: Remove -always-on property Message-ID: <20170121204302.ek2oovgay5odhdi3@rob-hp-laptop> References: <20170119104739.4376-1-bjorn.andersson@linaro.org> <20170119104739.4376-3-bjorn.andersson@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170119104739.4376-3-bjorn.andersson@linaro.org> User-Agent: Mutt/1.6.2-neo (2016-08-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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) 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. > > Cc: Subhash Jadavani > Cc: Vivek Gautam > Signed-off-by: Bjorn Andersson > --- > Documentation/devicetree/bindings/ufs/ufs-qcom.txt | 1 - > drivers/phy/phy-qcom-ufs-i.h | 1 - > drivers/phy/phy-qcom-ufs.c | 5 +---- > 3 files changed, 1 insertion(+), 6 deletions(-) Acked-by: Rob Herring