All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alina Yu <alina_yu@richtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <linux-kernel@vger.kernel.org>,
	<johnny_lai@richtek.com>, <cy_huang@richtek.com>
Subject: Re: [PATCH v2 2/4] regulator: rtq2208: Fix LDO to be compatible with both fixed and adjustable vout
Date: Wed, 8 May 2024 14:54:02 +0800	[thread overview]
Message-ID: <20240508065402.GA7462@linuxcarl2.richtek.com> (raw)
In-Reply-To: <ZjjwFTtiopqsYdeJ@finisterre.sirena.org.uk>

On Mon, May 06, 2024 at 11:58:29PM +0900, Mark Brown wrote:
> On Fri, May 03, 2024 at 03:35:36PM +0800, Alina Yu wrote:
> > On Fri, May 03, 2024 at 10:41:04AM +0900, Mark Brown wrote:
> 
> > > That's a substantail reconfiguration of the regulator, it would be
> > > better to have an explicit property for these non-standard fixed
> > > voltages rather than trying to do this using constraints, or at the very
> > > least have validation that the values being set are supported by the
> > > hardware.  The code should also be very clear about what is going on.
> 
> > May I add the 'richtek,use-fix-dvs' property back ?
> 
> It sounds like it might be better to add a property specifying the
> specific fixed voltage rather than overloading the constraints for this
> purpose.

May I modify the code into this ?
I'll add 'richtek,fixed-microvolt' property in dtsi; remove 'regulator-min-microvolt' and 'regulator-max-microvolt'
to prevent fail caused by constraints->apply_uV.

+       u32 fixed_uV;
        int ret, i;

-               if (init_data->constraints.min_uV == init_data->constraints.max_uV) {
+               if (!of_property_read_u32(match->of_node, "richtek,fixed-microvolt", &fixed_uV)) {
			desc->n_voltages = 1;
-                       desc->fixed_uV = init_data->constraints.min_uV;
+                       desc->fixed_uV = fixed_uV;
			desc->ops = &rtq2208_regulator_ldo_fix_ops;
...

Thanks,
Alina


  reply	other threads:[~2024-05-08  6:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  9:58 [PATCH v2 0/4] Fix rtq2208 BUCK ramp_delay and LDO dvs setting Alina Yu
2024-04-30  9:58 ` [PATCH v2 1/4] regulator: rtq2208: Fix LDO discharge register and add vsel setting Alina Yu
2024-05-01 14:14   ` Mark Brown
2024-04-30  9:58 ` [PATCH v2 2/4] regulator: rtq2208: Fix LDO to be compatible with both fixed and adjustable vout Alina Yu
2024-05-01  2:19   ` Mark Brown
2024-05-02  7:30     ` Alina Yu
2024-05-02  9:26       ` Alina Yu
2024-05-03  1:41         ` Mark Brown
2024-05-03  7:35           ` Alina Yu
2024-05-06 14:58             ` Mark Brown
2024-05-08  6:54               ` Alina Yu [this message]
2024-05-08 11:53                 ` Mark Brown
2024-05-09  9:15                   ` Alina Yu
2024-05-09 15:40                     ` Mark Brown
2024-05-10 12:12                       ` Alina Yu
2024-05-03  1:37       ` Mark Brown
2024-04-30  9:58 ` [PATCH v2 3/4] regulator: rtq2208: Fix invalid memory access when devm_of_regulator_put_matches is called Alina Yu
2024-05-01  2:19   ` Mark Brown
2024-04-30  9:58 ` [PATCH v2 4/4] regulator: rtq2208: Fix the BUCK ramp_delay range to maximum of 16mVstep/us Alina Yu
2024-05-03  1:32 ` (subset) [PATCH v2 0/4] Fix rtq2208 BUCK ramp_delay and LDO dvs setting 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=20240508065402.GA7462@linuxcarl2.richtek.com \
    --to=alina_yu@richtek.com \
    --cc=broonie@kernel.org \
    --cc=cy_huang@richtek.com \
    --cc=johnny_lai@richtek.com \
    --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 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.