From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] ARM: dts: vf-colibri: add basic supply regulators
Date: Wed, 17 Feb 2016 13:52:07 -0800 [thread overview]
Message-ID: <a07b405a5c73b092eaa6422b8562b56f@agner.ch> (raw)
In-Reply-To: <CAOMZO5Bb1eGSinoNkUhB_2w8mWdA+RQA0Z4geJp8B-MfGryAHw@mail.gmail.com>
On 2016-02-16 16:28, Fabio Estevam wrote:
> On Tue, Feb 16, 2016 at 10:18 PM, Stefan Agner <stefan@agner.ch> wrote:
>
>> + reg_module_3v3: regulator-module-3v3 {
>> + compatible = "regulator-fixed";
>> + regulator-name = "+V3.3";
>> + regulator-min-microvolt = <3300000>;
>> + regulator-max-microvolt = <3300000>;
>> + regulator-always-on;
>
> This 'regulator-always-on' property can be removed.
>
>> + };
>> +
>> + reg_module_3v3_avdd: regulator-module-3v3-avdd {
>> + compatible = "regulator-fixed";
>> + regulator-name = "+V3.3_AVDD_AUDIO";
>> + regulator-min-microvolt = <3300000>;
>> + regulator-max-microvolt = <3300000>;
>> + regulator-always-on;
>
> Same here.
Hm, should I remove them also in Patch 1/3? It's a fixed regulator too,
hence I guess regulator-always-on is pointless there too...?
--
Stefan
next prev parent reply other threads:[~2016-02-17 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 0:18 [PATCH v2 1/3] ARM: dts: vf-colibri: remove regulator container node Stefan Agner
2016-02-17 0:18 ` [PATCH v2 2/3] ARM: dts: vf-colibri: add basic supply regulators Stefan Agner
2016-02-17 0:28 ` Fabio Estevam
2016-02-17 21:52 ` Stefan Agner [this message]
2016-02-17 22:29 ` Fabio Estevam
2016-02-17 0:18 ` [PATCH v2 3/3] ARM: dts: vf-colibri: add carrier boards 3.3V supply Stefan Agner
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=a07b405a5c73b092eaa6422b8562b56f@agner.ch \
--to=stefan@agner.ch \
--cc=linux-arm-kernel@lists.infradead.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).