From: Alina Yu <alina_yu@richtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<cy_huang@richtek.com>
Subject: Re: [PATCH 1/2] regulator: rtq2208: Add fixed LDO VOUT property and check that matches the constraints
Date: Wed, 29 May 2024 14:41:23 +0800 [thread overview]
Message-ID: <20240529064123.GA13317@linuxcarl2.richtek.com> (raw)
In-Reply-To: <c0c7a63d-e435-4778-ad4c-3d93f0215116@sirena.org.uk>
On Mon, May 27, 2024 at 02:00:47PM +0100, Mark Brown wrote:
> On Thu, May 16, 2024 at 05:20:33PM +0800, Alina Yu wrote:
> > A fixed LDO VOUT property has been added to specify the fixed_uV of the regulator_desc.
> > Additionally, a check has been included in this version
> > to ensure that the fixed_uV matches the constraints.
>
> This doesn't apply against current code, please check and resend.
Regarding the previous discussion in
https://lore.kernel.org/all/20240528060731.GA25526@linuxcarl2.richtek.com/
I found some patches missing in the linux-next tree.
So I merged the missing part in my latest resent sereies.
The issue has been addressed in
In '[RESEND 2/4] regulator: rtq2208: Fix LDO to be compatible with both fixed and adjustable vout'
https://lore.kernel.org/all/5ad4c7728c7fa7f6286db36b99d31c9d0f5d16c7.1716870419.git.alina_yu@richtek.com/
@@ -219,7 +219,7 @@ static const struct regulator_ops rtq2208_regulator_buck_ops = {
.set_suspend_mode = rtq2208_set_suspend_mode,
};
-static const struct regulator_ops rtq2208_regulator_ldo_ops = {
+static const struct regulator_ops rtq2208_regulator_ldo_fix_ops = {
.enable = regulator_enable_regmap,
.disable = regulator_disable_regmap,
.is_enabled = regulator_is_enabled_regmap,
...
Thanks,
Alina
next prev parent reply other threads:[~2024-05-29 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 9:20 [PATCH 0/2] Add specified fixed LDO VOUT propery Alina Yu
2024-05-16 9:20 ` [PATCH 1/2] regulator: rtq2208: Add fixed LDO VOUT property and check that matches the constraints Alina Yu
2024-05-27 13:00 ` Mark Brown
2024-05-28 6:07 ` Alina Yu
2024-05-29 6:41 ` Alina Yu [this message]
2024-05-16 9:20 ` [PATCH 2/2] regulator: dt-bindings: rtq2208: Add specified fixed LDO VOUT property Alina Yu
2024-05-16 12:34 ` Krzysztof Kozlowski
2024-05-22 9:03 ` Alina Yu
2024-05-22 9:27 ` Krzysztof Kozlowski
2024-05-22 9:45 ` Alina Yu
2024-05-22 11:35 ` Mark Brown
2024-05-22 13:29 ` Krzysztof Kozlowski
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=20240529064123.GA13317@linuxcarl2.richtek.com \
--to=alina_yu@richtek.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.