From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>,
linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, sameo@linux.intel.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
lee.jones@linaro.org
Subject: Re: [PATCH 5/6] mfd: devicetree: bindings: 88pm800: Add DT property for dual phase enable
Date: Mon, 13 Jul 2015 17:10:03 +0900 [thread overview]
Message-ID: <55A3725B.2040801@samsung.com> (raw)
In-Reply-To: <55A36DBF.5020100@linaro.org>
On 13.07.2015 16:50, Vaibhav Hiremath wrote:
>
>
> On Saturday 11 July 2015 12:46 PM, Krzysztof Kozlowski wrote:
>> W dniu 09.07.2015 o 20:47, Vaibhav Hiremath pisze:
>>> 88PM860 family of device supports dual phase mode on BUCK1 supply
>>> providing total 6A capacity.
>>> Note that by default they operate independently with 3A capacity.
>>>
>>> This patch adds the devicetree binding to enable this
>>> feature.
>>>
>>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>>> ---
>>> Documentation/devicetree/bindings/mfd/88pm800.txt | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/mfd/88pm800.txt
>>> b/Documentation/devicetree/bindings/mfd/88pm800.txt
>>> index ae1311c..c756b31 100644
>>> --- a/Documentation/devicetree/bindings/mfd/88pm800.txt
>>> +++ b/Documentation/devicetree/bindings/mfd/88pm800.txt
>>> @@ -15,6 +15,12 @@ Optional properties :
>>> CLK32K3 - for 88pm800
>>> CLK32K2 - for 88pm860
>>>
>>> + (Applicable only to PXA910 family):
>>> +
>>> + - marvell,88pm860-buck1-dualphase-en : If set, enable dual phase
>>> on BUCK1,
>>> + providing 6A capacity.
>>> + Without this both BUCK1A and BUCK1B operates independently with
>>> 3A capacity.
>>> +
>>
>> 1. How does this relates to regulator driver? The
>> drivers/regulator/88pm800.c defines constraints for regulator which may
>> be contradictory.
>>
>> 2. This looks like a job for regulator driver, not MFD. Then you could
>> use standard regulator bindings (setting maximum current to 6A would
>> change the regulator to different mode).
>
> Make sense. and even better.
>
> I believe you are referring to,
>
> regulator-min-microamp = <3000000>;
> regulator-max-microamp = <6000000>;
>
> And provide set_current_limit() callback, to set the dualphase.
>
> Just to clarify more on this,
>
> The DT property would look something like,
>
> regulators {
> compatible = "marvell,88pm80x-regulator";
>
> buck1a: BUCK1A {
> regulator-compatible = "buck1";
> regulator-min-microvolt = <600000>;
> regulator-max-microvolt = <1800000>;
>
> regulator-min-microamp = <3000000>;
> regulator-max-microamp = <6000000>;
>
> regulator-boot-on;
> regulator-always-on;
> };
>
> buck1b: BUCK1B {
> regulator-compatible = "buck1b";
> regulator-min-microvolt = <600000>;
> regulator-max-microvolt = <1800000>;
>
> regulator-min-microamp = <3000000>;
> regulator-max-microamp = <6000000>;
>
> regulator-boot-on;
> regulator-always-on;
> };
> };
>
>
> And for the platforms, where dual phase is not required,
> we can either choose not to set these properties or set it to
>
>
> regulator-min-microamp = <3000000>;
> regulator-max-microamp = <3000000>;
Yes, exactly. I only wonder if regulator core would support properly
such bindings - setting current limit for a voltage regulator. I didn't
tried this but it should work.
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-07-13 8:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 11:47 [PATCH 0/6] mfd: 88pm800: Add 88pm860 device support Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 1/6] mfd: 88pm80x: Add 88pm860 chip type support Vaibhav Hiremath
2015-07-11 6:54 ` Krzysztof Kozlowski
2015-07-09 11:47 ` [PATCH 2/6] mfd: 88pm800: Add init time initial configuration support Vaibhav Hiremath
2015-07-11 6:53 ` Krzysztof Kozlowski
2015-07-13 7:10 ` Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 3/6] mfd: devicetree: bindings: 88pm800: Add DT property for 32KHz output enable Vaibhav Hiremath
2015-07-11 7:11 ` Krzysztof Kozlowski
2015-07-13 7:24 ` Vaibhav Hiremath
2015-07-13 7:31 ` Krzysztof Kozlowski
2015-07-13 7:38 ` Vaibhav Hiremath
2015-07-13 7:44 ` Krzysztof Kozlowski
2015-07-09 11:47 ` [PATCH 4/6] mfd: 88pm800: Enable 32KHZ XO low jitter clock out Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 5/6] mfd: devicetree: bindings: 88pm800: Add DT property for dual phase enable Vaibhav Hiremath
2015-07-11 7:16 ` Krzysztof Kozlowski
2015-07-13 7:50 ` Vaibhav Hiremath
2015-07-13 8:10 ` Krzysztof Kozlowski [this message]
2015-07-13 14:27 ` Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 6/6] mfd: 88pm800: Add support for configuration of dual phase on BUCK1 Vaibhav Hiremath
2015-07-09 12:04 ` [PATCH 0/6] mfd: 88pm800: Add 88pm860 device support Krzysztof Kozlowski
2015-07-09 12:44 ` Vaibhav Hiremath
2015-07-09 12:53 ` Vaibhav Hiremath
2015-07-09 13:28 ` Krzysztof Kozlowski
2015-07-10 12:03 ` Vaibhav Hiremath
2015-07-11 6:46 ` 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=55A3725B.2040801@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.com \
--cc=vaibhav.hiremath@linaro.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).