Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752946AbcDXRBk (ORCPT ); Sun, 24 Apr 2016 13:01:40 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:36612 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752783AbcDXRBi (ORCPT ); Sun, 24 Apr 2016 13:01:38 -0400 Subject: Re: [PATCH 3/3] regulator: twl: Regulator mode should not depend on regulator enabled state To: Pavel Machek References: <1458980895-10240-1-git-send-email-ivo.g.dimitrov.75@gmail.com> <1458980895-10240-4-git-send-email-ivo.g.dimitrov.75@gmail.com> <20160424161155.GD8880@amd> Cc: tony@atomide.com, lgirdwood@gmail.com, broonie@kernel.org, sre@kernel.org, pali.rohar@gmail.com, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org From: Ivaylo Dimitrov Message-ID: <571CFBEE.6050608@gmail.com> Date: Sun, 24 Apr 2016 20:01:34 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160424161155.GD8880@amd> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1994 Lines: 57 Hi, On 24.04.2016 19:11, Pavel Machek wrote: > On Sat 2016-03-26 10:28:15, Ivaylo Dimitrov wrote: >> When machine constraints are applied, regulator framework first sets >> initial mode (if any) and then enables the regulator if needed. The current >> code in twl4030reg_set_mode always checks if the regulator is enabled >> before applying the mode. That results in -EACCES error returned for >> "always-on" regulators which have "initial-mode" set in the board DTS. Fix >> that by removing the unneeded check. > > Should we keep the check for the regulators that are _not_ always-on? > I don't think so, as there is no other way to set mode to a regulator but through regulator framework and board DTS (for twl4030 that is) - and this is done only once during boot, see https://lkml.org/lkml/2016/4/17/78 as well. So, no matter if the regulator is always-on or not, that check is redundant IMO. Ivo > >> Signed-off-by: Ivaylo Dimitrov >> --- >> drivers/regulator/twl-regulator.c | 8 -------- >> 1 file changed, 8 deletions(-) >> >> diff --git a/drivers/regulator/twl-regulator.c b/drivers/regulator/twl-regulator.c >> index be8d05e..d8f6ad6 100644 >> --- a/drivers/regulator/twl-regulator.c >> +++ b/drivers/regulator/twl-regulator.c >> @@ -371,7 +371,6 @@ static int twl4030reg_set_mode(struct regulator_dev *rdev, unsigned mode) >> { >> struct twlreg_info *info = rdev_get_drvdata(rdev); >> unsigned message; >> - int status; >> >> /* We can only set the mode through state machine commands... */ >> switch (mode) { >> @@ -385,13 +384,6 @@ static int twl4030reg_set_mode(struct regulator_dev *rdev, unsigned mode) >> return -EINVAL; >> } >> >> - /* Ensure the resource is associated with some group */ >> - status = twlreg_grp(rdev); >> - if (status < 0) >> - return status; >> - if (!(status & (P3_GRP_4030 | P2_GRP_4030 | P1_GRP_4030))) >> - return -EACCES; >> - >> return twl4030_send_pb_msg(message); >> } >> >