public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Morgan <macroalpha82@gmail.com>
To: Philippe Simons <simons.philippe@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	"open list:VOLTAGE AND CURRENT REGULATOR FRAMEWORK"
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: axp20x: AXP717: set ramp_delay
Date: Sat, 7 Dec 2024 11:40:35 -0600	[thread overview]
Message-ID: <67548894.050a0220.2032bf.693e@mx.google.com> (raw)
In-Reply-To: <20241206123751.981977-1-simons.philippe@gmail.com>

On Fri, Dec 06, 2024 at 01:37:51PM +0100, Philippe Simons wrote:
> AXP717 datasheet says that regulator ramp delay is 15.625 us/step,
> which is 10mV in our case.
> 
> Add a AXP_DESC_RANGES_DELAY macro and update AXP_DESC_RANGES macro to
> expand to AXP_DESC_RANGES_DELAY with ramp_delay = 0
> 
> Signed-off-by: Philippe Simons <simons.philippe@gmail.com>
> ---
>  drivers/regulator/axp20x-regulator.c | 23 +++++++++++++++--------
>  1 file changed, 15 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/regulator/axp20x-regulator.c b/drivers/regulator/axp20x-regulator.c
> index a8e91d9d0..8f035db13 100644
> --- a/drivers/regulator/axp20x-regulator.c
> +++ b/drivers/regulator/axp20x-regulator.c
> @@ -419,8 +419,8 @@
>  		.ops		= &axp20x_ops_fixed				\
>  	}
>  
> -#define AXP_DESC_RANGES(_family, _id, _match, _supply, _ranges, _n_voltages,	\
> -			_vreg, _vmask, _ereg, _emask)				\
> +#define AXP_DESC_RANGES_DELAY(_family, _id, _match, _supply, _ranges, _n_voltages,	\
> +			_vreg, _vmask, _ereg, _emask, _ramp_delay)	\
>  	[_family##_##_id] = {							\
>  		.name		= (_match),					\
>  		.supply_name	= (_supply),					\
> @@ -437,8 +437,15 @@
>  		.linear_ranges	= (_ranges),					\
>  		.n_linear_ranges = ARRAY_SIZE(_ranges),				\
>  		.ops		= &axp20x_ops_range,				\
> +		.ramp_delay = (_ramp_delay),			\
>  	}
>  
> +#define AXP_DESC_RANGES(_family, _id, _match, _supply, _ranges, _n_voltages,	\
> +			_vreg, _vmask, _ereg, _emask)				\
> +	AXP_DESC_RANGES_DELAY(_family, _id, _match, _supply, _ranges, _n_voltages,	\
> +		_vreg, _vmask, _ereg, _emask, 0)
> +
> +
>  static const int axp209_dcdc2_ldo3_slew_rates[] = {
>  	1600,
>  	 800,
> @@ -781,18 +788,18 @@ static const struct linear_range axp717_dcdc3_ranges[] = {
>  };
>  
>  static const struct regulator_desc axp717_regulators[] = {
> -	AXP_DESC_RANGES(AXP717, DCDC1, "dcdc1", "vin1",
> +	AXP_DESC_RANGES_DELAY(AXP717, DCDC1, "dcdc1", "vin1",
>  			axp717_dcdc1_ranges, AXP717_DCDC1_NUM_VOLTAGES,
>  			AXP717_DCDC1_CONTROL, AXP717_DCDC_V_OUT_MASK,
> -			AXP717_DCDC_OUTPUT_CONTROL, BIT(0)),
> -	AXP_DESC_RANGES(AXP717, DCDC2, "dcdc2", "vin2",
> +			AXP717_DCDC_OUTPUT_CONTROL, BIT(0), 640),
> +	AXP_DESC_RANGES_DELAY(AXP717, DCDC2, "dcdc2", "vin2",
>  			axp717_dcdc2_ranges, AXP717_DCDC2_NUM_VOLTAGES,
>  			AXP717_DCDC2_CONTROL, AXP717_DCDC_V_OUT_MASK,
> -			AXP717_DCDC_OUTPUT_CONTROL, BIT(1)),
> -	AXP_DESC_RANGES(AXP717, DCDC3, "dcdc3", "vin3",
> +			AXP717_DCDC_OUTPUT_CONTROL, BIT(1), 640),
> +	AXP_DESC_RANGES_DELAY(AXP717, DCDC3, "dcdc3", "vin3",
>  			axp717_dcdc3_ranges, AXP717_DCDC3_NUM_VOLTAGES,
>  			AXP717_DCDC3_CONTROL, AXP717_DCDC_V_OUT_MASK,
> -			AXP717_DCDC_OUTPUT_CONTROL, BIT(2)),
> +			AXP717_DCDC_OUTPUT_CONTROL, BIT(2), 640),
>  	AXP_DESC(AXP717, DCDC4, "dcdc4", "vin4", 1000, 3700, 100,
>  		 AXP717_DCDC4_CONTROL, AXP717_DCDC_V_OUT_MASK,
>  		 AXP717_DCDC_OUTPUT_CONTROL, BIT(3)),
> -- 
> 2.47.1
> 

This series solves the immediate crashes I get on startup when I use
schedutil as my cpu scheduler.

Tested-by: Chris Morgan <macromorgan@hotmail.com>

  parent reply	other threads:[~2024-12-07 17:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 12:37 [PATCH] regulator: axp20x: AXP717: set ramp_delay Philippe Simons
2024-12-06 12:48 ` Mark Brown
2024-12-06 12:54   ` Philippe Simons
2024-12-06 13:44     ` Mark Brown
2024-12-06 13:47       ` Philippe Simons
2024-12-07  3:58 ` Hironori KIKUCHI
2024-12-07  4:37 ` Chen-Yu Tsai
2024-12-07  9:18   ` Philippe Simons
2024-12-07 17:40 ` Chris Morgan [this message]
2024-12-10 13:00 ` Mark Brown

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=67548894.050a0220.2032bf.693e@mx.google.com \
    --to=macroalpha82@gmail.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simons.philippe@gmail.com \
    --cc=wens@csie.org \
    /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