mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alina Yu <alina_yu@richtek.com>,
	lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	cy_huang@richtek.com
Subject: Re: [PATCH 2/2] regulator: dt-bindings: rtq2208: Add specified fixed LDO VOUT property
Date: Thu, 16 May 2024 14:34:02 +0200	[thread overview]
Message-ID: <5d26b19c-7679-4dba-a9ba-a7368d39b474@linaro.org> (raw)
In-Reply-To: <9c1bbe4b38a4ee5650d888478f1ce2cec2733669.1715846612.git.alina_yu@richtek.com>

On 16/05/2024 11:20, Alina Yu wrote:
> As the fixed voltage for the LDO is outside the range of the adjustable voltage mode,
> the constraints for this scenario are not suitable to represent both modes.
> Therefore, A property is added to specify the fixed LDO VOUT.
> 
> Examples of fixed LDO VOUT and adjustable LDO VOUT is also added to this version.
> 
> Signed-off-by: Alina Yu <alina_yu@richtek.com>
> ---

This is a v1 but I am pretty sure I saw it somewhere and there was
already some sort of discussion. Confused... :(

Best regards,
Krzysztof


  reply	other threads:[~2024-05-16 12:34 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
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 [this message]
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=5d26b19c-7679-4dba-a9ba-a7368d39b474@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=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 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®