public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, broonie@kernel.org, lgirdwood@gmail.com,
	patches@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] mfd: arizona: Factor out SYSCLK enable from wm5102 hardware patch
Date: Mon, 30 Mar 2015 12:22:55 +0100	[thread overview]
Message-ID: <20150330112255.GB9447@x1> (raw)
In-Reply-To: <1427127589-18297-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On Mon, 23 Mar 2015, Charles Keepax wrote:

> wm5102 applies a custom hardware boot sequence, for this the SYSCLK
> needs to be enabled. This patch factors out the code that enables
> SYSCLK for this sequence such that it can be used for other boot time
> operations that require SYSCLK.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> 
> Changes since v3:
>  - Split out enable and disable for the freerunning SYSCLK instead
>    of having a single function that takes a function pointer.
>  - Improve some naming for the sake of clarity
>  - Update error handling to use if (err) rather than if (err != 0)
>  - Added comment on register patch
> 
> Thanks,
> Charles
> 
>  drivers/mfd/arizona-core.c |  103 ++++++++++++++++++++++++++++++-------------
>  1 files changed, 72 insertions(+), 31 deletions(-)
> 
> diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
> index 6ca6dfa..695c68e 100644
> --- a/drivers/mfd/arizona-core.c
> +++ b/drivers/mfd/arizona-core.c
> @@ -250,20 +250,26 @@ static int arizona_wait_for_boot(struct arizona *arizona)
>  	return ret;
>  }
>  
> -static int arizona_apply_hardware_patch(struct arizona* arizona)
> +struct arizona_sysclk_state {
> +	unsigned int fll;
> +	unsigned int sysclk;
> +};
> +
> +static int arizona_enable_freerun_sysclk(struct arizona *arizona,
> +					 struct arizona_sysclk_state *state)
>  {
> -	unsigned int fll, sysclk;
>  	int ret, err;
>  
>  	/* Cache existing FLL and SYSCLK settings */
> -	ret = regmap_read(arizona->regmap, ARIZONA_FLL1_CONTROL_1, &fll);
> -	if (ret != 0) {
> +	ret = regmap_read(arizona->regmap, ARIZONA_FLL1_CONTROL_1, &state->fll);
> +	if (ret) {
>  		dev_err(arizona->dev, "Failed to cache FLL settings: %d\n",
>  			ret);
>  		return ret;
>  	}
> -	ret = regmap_read(arizona->regmap, ARIZONA_SYSTEM_CLOCK_1, &sysclk);
> -	if (ret != 0) {
> +	ret = regmap_read(arizona->regmap, ARIZONA_SYSTEM_CLOCK_1,
> +			  &state->sysclk);
> +	if (ret) {
>  		dev_err(arizona->dev, "Failed to cache SYSCLK settings: %d\n",
>  			ret);
>  		return ret;
> @@ -272,7 +278,7 @@ static int arizona_apply_hardware_patch(struct arizona* arizona)
>  	/* Start up SYSCLK using the FLL in free running mode */
>  	ret = regmap_write(arizona->regmap, ARIZONA_FLL1_CONTROL_1,
>  			ARIZONA_FLL1_ENA | ARIZONA_FLL1_FREERUN);
> -	if (ret != 0) {
> +	if (ret) {
>  		dev_err(arizona->dev,
>  			"Failed to start FLL in freerunning mode: %d\n",
>  			ret);
> @@ -281,50 +287,85 @@ static int arizona_apply_hardware_patch(struct arizona* arizona)
>  	ret = arizona_poll_reg(arizona, 25, ARIZONA_INTERRUPT_RAW_STATUS_5,
>  			       ARIZONA_FLL1_CLOCK_OK_STS,
>  			       ARIZONA_FLL1_CLOCK_OK_STS);
> -	if (ret != 0) {
> +	if (ret) {
>  		ret = -ETIMEDOUT;
>  		goto err_fll;
>  	}
>  
>  	ret = regmap_write(arizona->regmap, ARIZONA_SYSTEM_CLOCK_1, 0x0144);
> -	if (ret != 0) {
> +	if (ret) {
>  		dev_err(arizona->dev, "Failed to start SYSCLK: %d\n", ret);
>  		goto err_fll;
>  	}
>  
> +	return 0;
> +
> +err_fll:
> +	err = regmap_write(arizona->regmap, ARIZONA_FLL1_CONTROL_1, state->fll);
> +	if (err)
> +		dev_err(arizona->dev,
> +			"Failed to re-apply old FLL settings: %d\n",
> +			err);

Nit: How is it that the regmap_write() line fit on 80 chars and the
"err);" bit can't?

> +	return ret;
> +}
> +
> +static int arizona_disable_freerun_sysclk(struct arizona *arizona,
> +					  struct arizona_sysclk_state *state)
> +{
> +	int ret = 0;
> +	int err;
> +
> +	err = regmap_write(arizona->regmap, ARIZONA_SYSTEM_CLOCK_1,
> +			   state->sysclk);
> +	if (err) {
> +		dev_err(arizona->dev,
> +			"Failed to re-apply old SYSCLK settings: %d\n",
> +			err);

Same there, this extra linewrap seems unnecessary.

> +		ret = err;
> +	}

Can you explain the resson for using 'err' and and not 'ret'?

> +	err = regmap_write(arizona->regmap, ARIZONA_FLL1_CONTROL_1, state->fll);
> +	if (err) {
> +		dev_err(arizona->dev,
> +			"Failed to re-apply old FLL settings: %d\n",
> +			err);
> +		ret = err;
> +	}
> +
> +	return ret;
> +}
> +
> +static int wm5102_apply_hardware_patch(struct arizona *arizona)
> +{
> +	struct arizona_sysclk_state state;
> +	int err, ret;
> +
> +	ret = arizona_enable_freerun_sysclk(arizona, &state);
> +	if (ret)
> +		return ret;
> +
>  	/* Start the write sequencer and wait for it to finish */
>  	ret = regmap_write(arizona->regmap, ARIZONA_WRITE_SEQUENCER_CTRL_0,
>  			ARIZONA_WSEQ_ENA | ARIZONA_WSEQ_START | 160);
> -	if (ret != 0) {
> +	if (ret) {
>  		dev_err(arizona->dev, "Failed to start write sequencer: %d\n",
>  			ret);
> -		goto err_sysclk;
> +		goto err;
>  	}
> +
>  	ret = arizona_poll_reg(arizona, 5, ARIZONA_WRITE_SEQUENCER_CTRL_1,
>  			       ARIZONA_WSEQ_BUSY, 0);
> -	if (ret != 0) {
> +	if (ret) {
>  		regmap_write(arizona->regmap, ARIZONA_WRITE_SEQUENCER_CTRL_0,
> -				ARIZONA_WSEQ_ABORT);
> +			     ARIZONA_WSEQ_ABORT);
>  		ret = -ETIMEDOUT;
>  	}
>  
> -err_sysclk:
> -	err = regmap_write(arizona->regmap, ARIZONA_SYSTEM_CLOCK_1, sysclk);
> -	if (err != 0) {
> -		dev_err(arizona->dev,
> -			"Failed to re-apply old SYSCLK settings: %d\n",
> -			err);
> -	}
> -
> -err_fll:
> -	err = regmap_write(arizona->regmap, ARIZONA_FLL1_CONTROL_1, fll);
> -	if (err != 0) {
> -		dev_err(arizona->dev,
> -			"Failed to re-apply old FLL settings: %d\n",
> -			err);
> -	}
> +err:
> +	err = arizona_disable_freerun_sysclk(arizona, &state);
>  
> -	if (ret != 0)
> +	if (ret)
>  		return ret;
>  	else
>  		return err;

return ret ?: err;

> @@ -366,7 +407,7 @@ static int arizona_runtime_resume(struct device *dev)
>  			goto err;
>  		}
>  
> -		ret = arizona_apply_hardware_patch(arizona);
> +		ret = wm5102_apply_hardware_patch(arizona);
>  		if (ret != 0) {
>  			dev_err(arizona->dev,
>  				"Failed to apply hardware patch: %d\n",
> @@ -891,7 +932,7 @@ int arizona_dev_init(struct arizona *arizona)
>  
>  		switch (arizona->type) {
>  		case WM5102:
> -			ret = arizona_apply_hardware_patch(arizona);
> +			ret = wm5102_apply_hardware_patch(arizona);
>  			if (ret != 0) {
>  				dev_err(arizona->dev,
>  					"Failed to apply hardware patch: %d\n",

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2015-03-30 11:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 16:19 [PATCH v3 1/4] mfd: arizona: Factor out SYSCLK enable from wm5102 hardware patch Charles Keepax
2015-03-23 16:19 ` [PATCH v3 2/4] mfd: wm5110: Add register patch required for low power sleep Charles Keepax
2015-03-30 11:24   ` Lee Jones
2015-03-23 16:19 ` [PATCH v3 3/4] regulator: arizona-ldo1: Add additional supported voltage Charles Keepax
2015-03-23 16:19 ` [PATCH v3 4/4] mfd: wm5110: Set DCVDD voltage to 1.175V before entering sleep mode Charles Keepax
2015-03-30 11:26   ` Lee Jones
2015-03-30 11:22 ` Lee Jones [this message]
2015-03-30 16:39   ` [PATCH v3 1/4] mfd: arizona: Factor out SYSCLK enable from wm5102 hardware patch Charles Keepax
2015-03-31  8:01     ` Lee Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150330112255.GB9447@x1 \
    --to=lee.jones@linaro.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=sameo@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox