mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maciej Purski <m.purski@samsung.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [RFC PATCH v2 1/3] regulator: bindings: Add properties for coupled regulators
Date: Wed, 25 Oct 2017 09:31:45 +0200	[thread overview]
Message-ID: <76404da2-fe50-b124-0f18-e93e3cb14014@samsung.com> (raw)
In-Reply-To: <20171024185801.bq27wszp7socsxqx@rob-hp-laptop>



On 10/24/2017 08:58 PM, Rob Herring wrote:
> On Wed, Oct 18, 2017 at 02:47:00PM +0200, Maciej Purski wrote:
>> Some regulators require keeping their voltage spread below defined
>> max_spread.
>>
>> Add properties to provide information on regulators' coupling.
>>
>> Signed-off-by: Maciej Purski <m.purski@samsung.com>
>> ---
>>   Documentation/devicetree/bindings/regulator/regulator.txt | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt
>> index 378f6dc..6769565 100644
>> --- a/Documentation/devicetree/bindings/regulator/regulator.txt
>> +++ b/Documentation/devicetree/bindings/regulator/regulator.txt
>> @@ -60,6 +60,10 @@ Optional properties:
>>   	0: Disable active discharge.
>>   	1: Enable active discharge.
>>   	Absence of this property will leave configuration to default.
>> +- regulator-coupled-with: Phandle to regulators with which the regulator
>> +  should be coupled. Allow up to 9 phandles.
> 
> 9? Sounds like a driver detail and pretty arbitrary.
> 
It's just a constant number that I defined as MAX_COUPLED, because in fact there 
isn't any use-case yet for even more than two regulators so MAX_COUPLED equal to 
9 is a really high number. If you find it cleaner, I can make this value variable.

> Is this linkage 2-way meaning 2 coupled regulators both have links to
> the other one? If so, then what happens when you have a high number? If
> not, how does one decide which regulator has this property?

Yes, it is 2-way. When you have a high number, then each regulator should have 
phandles to every other. So, if you have 3 regulators coupled, then each one 
should have 2 phandles.

> 
>> +- regulator-coupled-max-spread: Max spread between voltages of coupled regulators
>> +  in microvolts.
>>   
>>   Deprecated properties:
>>   - regulator-compatible: If a regulator chip contains multiple
>> -- 
>> 2.7.4
>>
> 
> 
> 

  reply	other threads:[~2017-10-25  7:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171018124722eucas1p23aa3280d33bfd38650783ac7f52b9909@eucas1p2.samsung.com>
2017-10-18 12:46 ` [RFC PATCH v2 0/3] Add coupled regulators mechanism Maciej Purski
     [not found]   ` <CGME20171018124727eucas1p255ccce41852d5585640f2d97153d2fa8@eucas1p2.samsung.com>
2017-10-18 12:47     ` [RFC PATCH v2 1/3] regulator: bindings: Add properties for coupled regulators Maciej Purski
2017-10-24 18:58       ` Rob Herring
2017-10-25  7:31         ` Maciej Purski [this message]
2017-10-25 12:59           ` Rob Herring
2017-10-25 13:10             ` Maciej Purski
     [not found]   ` <CGME20171018124735eucas1p2dc60191fb185f18dee16d4b3de8502cf@eucas1p2.samsung.com>
2017-10-18 12:47     ` [RFC PATCH v2 2/3] regulator: core: Parse coupled regulators properties Maciej Purski
2017-11-29 16:25       ` Mark Brown
     [not found]   ` <CGME20171018124737eucas1p2ed8002fa4910545e9d56a536303ffc12@eucas1p2.samsung.com>
2017-10-18 12:47     ` [RFC PATCH v2 3/3] regulator: core: Balance coupled regulators voltages Maciej Purski
2017-11-29 18:29       ` 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=76404da2-fe50-b124-0f18-e93e3cb14014@samsung.com \
    --to=m.purski@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=robh@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®