From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Kalle Niemi <kaleposti@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: bd71815: fix ramp values
Date: Wed, 12 Jun 2024 14:47:40 +0300 [thread overview]
Message-ID: <9e9f27dc-80fb-4f0d-a29d-b418a7e96042@gmail.com> (raw)
In-Reply-To: <ZmmJXtuVJU6RgQAH@latitude5580>
Hi Kalle,
Thanks for finding and fixing this!
On 6/12/24 14:42, Kalle Niemi wrote:
> Ramp values are inverted. This caused wrong values written to register
> when ramp values were defined in device tree.
>
> Invert values in table to fix this.
>
> Signed-off-by: Kalle Niemi <kaleposti@gmail.com>
Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
> Fixes: 1aad39001e85 ("regulator: Support ROHM BD71815 regulators")
> ---
> drivers/regulator/bd71815-regulator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/regulator/bd71815-regulator.c b/drivers/regulator/bd71815-regulator.c
> index 26192d55a685..79fbb45297f6 100644
> --- a/drivers/regulator/bd71815-regulator.c
> +++ b/drivers/regulator/bd71815-regulator.c
> @@ -256,7 +256,7 @@ static int buck12_set_hw_dvs_levels(struct device_node *np,
> * 10: 2.50mV/usec 10mV 4uS
> * 11: 1.25mV/usec 10mV 8uS
> */
> -static const unsigned int bd7181x_ramp_table[] = { 1250, 2500, 5000, 10000 };
> +static const unsigned int bd7181x_ramp_table[] = { 10000, 5000, 2500, 1250 };
>
> static int bd7181x_led_set_current_limit(struct regulator_dev *rdev,
> int min_uA, int max_uA)
>
> base-commit: 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2024-06-12 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 11:42 Kalle Niemi
2024-06-12 11:47 ` Matti Vaittinen [this message]
2024-06-12 17:09 ` 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=9e9f27dc-80fb-4f0d-a29d-b418a7e96042@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=broonie@kernel.org \
--cc=kaleposti@gmail.com \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®