All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Crispin <blogic@openwrt.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V6 1/2] regulator: Add document for MT6323 regulator
Date: Thu, 18 Feb 2016 15:50:10 +0100	[thread overview]
Message-ID: <56C5DA22.9080008@openwrt.org> (raw)
In-Reply-To: <20160218143610.GG9654@rob-hp-laptop>



On 18/02/2016 15:36, Rob Herring wrote:
> On Wed, Feb 17, 2016 at 12:37:35PM +0100, John Crispin wrote:
>> Signed-off-by: John Crispin <blogic@openwrt.org>
>> Cc: devicetree@vger.kernel.org
>>
>> ---
>> Changes in V6
>> * remove the compatible string
>>
>> Changes in V5
>> * regulator vs regulators
>>
>> Changes in V4
>> * regulator is a subnode and not a property
>>
>>  .../bindings/regulator/mt6323-regulator.txt        |  241 ++++++++++++++++++++
>>  1 file changed, 241 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/regulator/mt6323-regulator.txt
>>
>> diff --git a/Documentation/devicetree/bindings/regulator/mt6323-regulator.txt b/Documentation/devicetree/bindings/regulator/mt6323-regulator.txt
>> new file mode 100644
>> index 0000000..67c0780
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/regulator/mt6323-regulator.txt
>> @@ -0,0 +1,241 @@
>> +Mediatek MT6323 Regulator Driver
>> +
>> +All voltage regulators are defined as subnodes of the regulators node. A list
>> +of regulators provided by this controller are defined as subnodes of the
>> +drivers node. Each regulator is named according to its regulator type,
> 
> s/drivers/PMIC's/
> 
>> +buck_<name> and ldo_<name>. The definition for each of these nodes is defined
>> +using the standard binding for regulators at
>> +Documentation/devicetree/bindings/regulator/regulator.txt.
>> +
>> +The valid names for regulators are::
>> +BUCK:
>> +  buck_vproc, buck_vsys, buck_vpa
>> +LDO:
>> +  ldo_vtcxo, ldo_vcn28, ldo_vcn33_bt, ldo_vcn33_wifi, ldo_va, ldo_vcama,
>> +  ldo_vio28, ldo_vusb, ldo_vmc, ldo_vmch, ldo_vemc3v3, ldo_vgp1, ldo_vgp2,
>> +  ldo_vgp3, ldo_vcn18, ldo_vsim1, ldo_vsim2, ldo_vrtc, ldo_vcamaf, ldo_vibr,
>> +  ldo_vrf18, ldo_vm, ldo_vio18, ldo_vcamd, ldo_vcamio
>> +
>> +Example:
>> +
>> +	pmic: mt6323 {
>> +		compatible = "mediatek,mt6323";
>> +
>> +		mt6323regulator: regulators {
>> +			compatible = "mediatek,mt6323-regulator";
> 
> Still have the compatible here...
> 
> Otherwise:
> 
> Acked-by: Rob Herring <robh@kernel.org>
> 

grml, i only removed one of the compat strings and did not notice there
are two. do you want me to send a fixup that you can fold into the one
you already merged or do you want me to resend just this one patch with
the fix applied ?

	John


> 
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
> 

WARNING: multiple messages have this Message-ID (diff)
From: blogic@openwrt.org (John Crispin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6 1/2] regulator: Add document for MT6323 regulator
Date: Thu, 18 Feb 2016 15:50:10 +0100	[thread overview]
Message-ID: <56C5DA22.9080008@openwrt.org> (raw)
In-Reply-To: <20160218143610.GG9654@rob-hp-laptop>



On 18/02/2016 15:36, Rob Herring wrote:
> On Wed, Feb 17, 2016 at 12:37:35PM +0100, John Crispin wrote:
>> Signed-off-by: John Crispin <blogic@openwrt.org>
>> Cc: devicetree at vger.kernel.org
>>
>> ---
>> Changes in V6
>> * remove the compatible string
>>
>> Changes in V5
>> * regulator vs regulators
>>
>> Changes in V4
>> * regulator is a subnode and not a property
>>
>>  .../bindings/regulator/mt6323-regulator.txt        |  241 ++++++++++++++++++++
>>  1 file changed, 241 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/regulator/mt6323-regulator.txt
>>
>> diff --git a/Documentation/devicetree/bindings/regulator/mt6323-regulator.txt b/Documentation/devicetree/bindings/regulator/mt6323-regulator.txt
>> new file mode 100644
>> index 0000000..67c0780
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/regulator/mt6323-regulator.txt
>> @@ -0,0 +1,241 @@
>> +Mediatek MT6323 Regulator Driver
>> +
>> +All voltage regulators are defined as subnodes of the regulators node. A list
>> +of regulators provided by this controller are defined as subnodes of the
>> +drivers node. Each regulator is named according to its regulator type,
> 
> s/drivers/PMIC's/
> 
>> +buck_<name> and ldo_<name>. The definition for each of these nodes is defined
>> +using the standard binding for regulators at
>> +Documentation/devicetree/bindings/regulator/regulator.txt.
>> +
>> +The valid names for regulators are::
>> +BUCK:
>> +  buck_vproc, buck_vsys, buck_vpa
>> +LDO:
>> +  ldo_vtcxo, ldo_vcn28, ldo_vcn33_bt, ldo_vcn33_wifi, ldo_va, ldo_vcama,
>> +  ldo_vio28, ldo_vusb, ldo_vmc, ldo_vmch, ldo_vemc3v3, ldo_vgp1, ldo_vgp2,
>> +  ldo_vgp3, ldo_vcn18, ldo_vsim1, ldo_vsim2, ldo_vrtc, ldo_vcamaf, ldo_vibr,
>> +  ldo_vrf18, ldo_vm, ldo_vio18, ldo_vcamd, ldo_vcamio
>> +
>> +Example:
>> +
>> +	pmic: mt6323 {
>> +		compatible = "mediatek,mt6323";
>> +
>> +		mt6323regulator: regulators {
>> +			compatible = "mediatek,mt6323-regulator";
> 
> Still have the compatible here...
> 
> Otherwise:
> 
> Acked-by: Rob Herring <robh@kernel.org>
> 

grml, i only removed one of the compat strings and did not notice there
are two. do you want me to send a fixup that you can fold into the one
you already merged or do you want me to resend just this one patch with
the fix applied ?

	John


> 
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
> 

  reply	other threads:[~2016-02-18 14:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 11:37 [PATCH V6 1/2] regulator: Add document for MT6323 regulator John Crispin
2016-02-17 11:37 ` John Crispin
2016-02-17 11:37 ` John Crispin
2016-02-17 11:37 ` [PATCH V6 2/2] regulator: mt6323: Add support " John Crispin
2016-02-17 11:37   ` John Crispin
2016-02-17 19:13   ` Applied "regulator: mt6323: Add support for MT6323 regulator" to the regulator tree Mark Brown
2016-03-15  9:29   ` Mark Brown
2016-03-15  9:32     ` Mark Brown
2016-03-15  9:52       ` John Crispin
2016-02-17 19:13 ` Applied "regulator: Add document " Mark Brown
2016-02-18 14:36 ` [PATCH V6 1/2] regulator: Add document for MT6323 regulator Rob Herring
2016-02-18 14:36   ` Rob Herring
2016-02-18 14:50   ` John Crispin [this message]
2016-02-18 14:50     ` John Crispin
2016-02-21  0:38 ` Mark Brown
2016-02-21  0:38   ` Mark Brown
2016-02-21  0:38   ` Mark Brown
2016-03-15  9:29 ` Applied "regulator: Add document for MT6323 regulator" to the regulator tree 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=56C5DA22.9080008@openwrt.org \
    --to=blogic@openwrt.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.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 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.