From: skakit@codeaurora.org
To: Mark Brown <broonie@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
mka@chromium.org, swboyd@chromium.org,
Das Srinagesh <gurus@codeaurora.org>,
David Collins <collinsd@codeaurora.org>,
kgunda@codeaurora.org,
Subbaraman Narayanamurthy <subbaram@codeaurora.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] regulator: dt-bindings: Add pm8008 regulator bindings
Date: Tue, 28 Sep 2021 18:14:16 +0530 [thread overview]
Message-ID: <b192c1e056e0ea2fc959651065e4ce7b@codeaurora.org> (raw)
In-Reply-To: <20210917154818.GC4700@sirena.org.uk>
On 2021-09-17 21:18, Mark Brown wrote:
> On Fri, Sep 17, 2021 at 04:15:36PM +0530, Satya Priya wrote:
>
>> + properties:
>> + reg:
>> + maxItems: 1
>> + regulator-name: true
>> + regulator-min-microvolt: true
>> + regulator-max-microvolt: true
>
> You shouldn't be forcing these properties, it should be perfectly OK
> for
> boards to have fixed voltages especially for example during bringup or
> for debugging.
>
Okay. I will remove these.
>> + qcom,min-dropout-voltage:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description:
>> + Specifies the minimum voltage in microvolts that the parent
>> + supply regulator must output, above the output of this
>> + regulator.
>
> If this is needed in DT it should be a generic property since most
> regulators have some requirement here however usually it's a fixed
> property of the silicon and should therefore just gets set in the
> regulator_desc as min_dropout_uV - I'd strongly recommend having a
> default there even if there's some requirement for it to be set per
> board.
Yeah, we are setting the default values for this(headroom_uv) from
driver. Please see below
struct regulator_data {
char *name;
char *supply_name;
int min_uv;
int max_uv;
int min_dropout_uv;
};
static const struct regulator_data reg_data[PM8008_MAX_LDO] = {
/* name parent min_uv max_uv headroom_uv */
{"l1", "vdd_l1_l2", 528000, 1504000, 225000},
{"l2", "vdd_l1_l2", 528000, 1504000, 225000},
{"l3", "vdd_l3_l4", 1504000, 3400000, 200000},
{"l4", "vdd_l3_l4", 1504000, 3400000, 200000},
{"l5", "vdd_l5", 1504000, 3400000, 300000},
{"l6", "vdd_l6", 1504000, 3400000, 300000},
{"l7", "vdd_l7", 1504000, 3400000, 300000},
};
Inside Register LDO API:
pm8008_reg->rdesc.min_dropout_uV = reg_data[i].min_dropout_uv;
of_property_read_u32(reg_node, "qcom,min-dropout-voltage",
&pm8008_reg->rdesc.min_dropout_uV);
next prev parent reply other threads:[~2021-09-28 12:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 10:45 [PATCH 0/4] Add Qualcomm Technologies, Inc. PM8008 regulator driver Satya Priya
2021-09-17 10:45 ` [PATCH 1/4] dt-bindings: mfd: pm8008: Add pm8008 regulator node Satya Priya
2021-09-17 19:48 ` Rob Herring
2021-09-20 19:32 ` Stephen Boyd
2021-09-28 12:31 ` skakit
2021-09-20 20:40 ` Rob Herring
2021-09-28 12:43 ` skakit
2021-09-17 10:45 ` [PATCH 2/4] regulator: dt-bindings: Add pm8008 regulator bindings Satya Priya
2021-09-17 15:48 ` Mark Brown
2021-09-28 12:44 ` skakit [this message]
2021-09-17 10:45 ` [PATCH 3/4] regulator: Add a regulator driver for the PM8008 PMIC Satya Priya
2021-09-17 15:38 ` Mark Brown
2021-09-28 12:16 ` skakit
2021-09-17 10:45 ` [PATCH 4/4] arm64: dts: qcom: sc7280: Add pm8008 regulators support for sc7280-idp Satya Priya
2021-09-20 19:37 ` Stephen Boyd
2021-09-28 12:42 ` skakit
2021-09-17 11:01 ` [PATCH 0/4] Add Qualcomm Technologies, Inc. PM8008 regulator driver skakit
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=b192c1e056e0ea2fc959651065e4ce7b@codeaurora.org \
--to=skakit@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=gurus@codeaurora.org \
--cc=kgunda@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=subbaram@codeaurora.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).