Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mikhail Rudenko <mike.rudenko@gmail.com>
To: linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Alex Bee <knaerzche@gmail.com>,
	Lee Jones <lee@kernel.org>,
	Quentin Schulz <foss+kernel@0leil.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	Chris Zhong <zyw@rock-chips.com>,
	Zhang Qing <zhangqing@rock-chips.com>,
	Mikhail Rudenko <mike.rudenko@gmail.com>
Subject: Re: [PATCH] regulator: rk808: Add apply_bit for BUCK3 on RK809
Date: Mon, 28 Oct 2024 18:20:55 +0300	[thread overview]
Message-ID: <87v7xcp7bh.fsf@gmail.com> (raw)
In-Reply-To: <20241017-rk809-dcdc3-v1-1-e3c3de92f39c@gmail.com>

Gentle ping.

Also Cc more potential reviewers.

On 2024-10-17 at 21:37 +03, Mikhail Rudenko <mike.rudenko@gmail.com> wrote:

> Currently, RK809's BUCK3 regulator is modelled in the driver as a
> configurable regulator with 0.5-2.4V voltage range. But the voltage
> setting is not actually applied, because when bit 6 of
> PMIC_POWER_CONFIG register is set to 0 (default), BUCK3 output voltage
> is determined by the external feedback resistor. Fix this, by setting
> bit 6 when voltage selection is set. Existing users which do not
> specify voltage constraints in their device trees will not be affected
> by this change, since no voltage setting is applied in those cases,
> and bit 6 is not enabled.
>
> Signed-off-by: Mikhail Rudenko <mike.rudenko@gmail.com>
> ---
>  drivers/regulator/rk808-regulator.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/regulator/rk808-regulator.c b/drivers/regulator/rk808-regulator.c
> index 14b60abd6afc..01a8d0487918 100644
> --- a/drivers/regulator/rk808-regulator.c
> +++ b/drivers/regulator/rk808-regulator.c
> @@ -1379,6 +1379,8 @@ static const struct regulator_desc rk809_reg[] = {
>  		.n_linear_ranges = ARRAY_SIZE(rk817_buck1_voltage_ranges),
>  		.vsel_reg = RK817_BUCK3_ON_VSEL_REG,
>  		.vsel_mask = RK817_BUCK_VSEL_MASK,
> +		.apply_reg = RK817_POWER_CONFIG,
> +		.apply_bit = RK817_BUCK3_FB_RES_INTER,
>  		.enable_reg = RK817_POWER_EN_REG(0),
>  		.enable_mask = ENABLE_MASK(RK817_ID_DCDC3),
>  		.enable_val = ENABLE_MASK(RK817_ID_DCDC3),
>
> ---
> base-commit: 9852d85ec9d492ebef56dc5f229416c925758edc
> change-id: 20241017-rk809-dcdc3-388632b4da03
>

--
Best regards,
Mikhail Rudenko


       reply	other threads:[~2024-10-28 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241017-rk809-dcdc3-v1-1-e3c3de92f39c@gmail.com>
2024-10-28 15:20 ` Mikhail Rudenko [this message]
2024-10-28 15:39   ` [PATCH] regulator: rk808: Add apply_bit for BUCK3 on RK809 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=87v7xcp7bh.fsf@gmail.com \
    --to=mike.rudenko@gmail.com \
    --cc=broonie@kernel.org \
    --cc=foss+kernel@0leil.net \
    --cc=knaerzche@gmail.com \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=zhangqing@rock-chips.com \
    --cc=zyw@rock-chips.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