From: dinguyen@opensource.altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/2] ARM: dts: socfpga: Add a 3.3V fixed regulator node
Date: Mon, 20 Oct 2014 16:02:41 -0500 [thread overview]
Message-ID: <54457871.404@opensource.altera.com> (raw)
In-Reply-To: <CAD=FV=XzQ0JHpNsu+fyuRGi6NHeVxwNdxuGTPny3+dbTDYCo5g@mail.gmail.com>
On 10/20/2014 10:51 AM, Doug Anderson wrote:
> Dinh,
>
> On Mon, Oct 20, 2014 at 8:31 AM, <dinguyen@opensource.altera.com> wrote:
>> +++ b/arch/arm/boot/dts/socfpga_arria5_socdk.dts
>> @@ -37,6 +37,15 @@
>> */
>> ethernet0 = &gmac1;
>> };
>> +
>> + regulator_3_3v: regulator {
>
> I think it's better to give this a real node name. The
> "regulator_3_3v" will get dropped when you compile this into a binary
> format (for shipping), so you're creating a node that's just called
> "regulator". If you had more than one fixed regulator like this it
> just won't work.
>
> I haven't seen any official guidelines, but I tend to use "regulator"
> as a suffix and then put the schematic name. Like:
>
> 3_3v_regulator: 3-3-v-regulator
>
>
Not sure if there's a limit on a node cannot start with numeric value?
But if I change it to your suggestion, the DTC does not compile:
Error: arch/arm/boot/dts/socfpga_cyclone5_socdk.dts:41.16-17 syntax error
FATAL ERROR: Unable to parse input tree
But regulator_3_3v: 3-3-v-regulator will work fine.
Dinh
WARNING: multiple messages have this Message-ID (diff)
From: Dinh Nguyen <dinguyen-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
To: Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Jaehoon Chung
<jh80.chung-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
Dinh Nguyen <dinh.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org,
s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org
Subject: Re: [PATCHv2 2/2] ARM: dts: socfpga: Add a 3.3V fixed regulator node
Date: Mon, 20 Oct 2014 16:02:41 -0500 [thread overview]
Message-ID: <54457871.404@opensource.altera.com> (raw)
In-Reply-To: <CAD=FV=XzQ0JHpNsu+fyuRGi6NHeVxwNdxuGTPny3+dbTDYCo5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 10/20/2014 10:51 AM, Doug Anderson wrote:
> Dinh,
>
> On Mon, Oct 20, 2014 at 8:31 AM, <dinguyen-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org> wrote:
>> +++ b/arch/arm/boot/dts/socfpga_arria5_socdk.dts
>> @@ -37,6 +37,15 @@
>> */
>> ethernet0 = &gmac1;
>> };
>> +
>> + regulator_3_3v: regulator {
>
> I think it's better to give this a real node name. The
> "regulator_3_3v" will get dropped when you compile this into a binary
> format (for shipping), so you're creating a node that's just called
> "regulator". If you had more than one fixed regulator like this it
> just won't work.
>
> I haven't seen any official guidelines, but I tend to use "regulator"
> as a suffix and then put the schematic name. Like:
>
> 3_3v_regulator: 3-3-v-regulator
>
>
Not sure if there's a limit on a node cannot start with numeric value?
But if I change it to your suggestion, the DTC does not compile:
Error: arch/arm/boot/dts/socfpga_cyclone5_socdk.dts:41.16-17 syntax error
FATAL ERROR: Unable to parse input tree
But regulator_3_3v: 3-3-v-regulator will work fine.
Dinh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-20 21:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 15:31 [PATCHv2 0/2] ARM: dts: socfpga: fix booting with SD/MMC dinguyen at opensource.altera.com
2014-10-20 15:31 ` dinguyen
2014-10-20 15:31 ` [PATCHv2 1/2] ARM: dts: socfpga: Fix SD card detect dinguyen at opensource.altera.com
2014-10-20 15:31 ` dinguyen
2014-10-20 15:46 ` Doug Anderson
2014-10-20 15:46 ` Doug Anderson
2014-10-20 16:31 ` Dinh Nguyen
2014-10-20 16:31 ` Dinh Nguyen
2014-10-20 19:30 ` Doug Anderson
2014-10-20 19:30 ` Doug Anderson
2014-10-20 19:48 ` Doug Anderson
2014-10-20 19:48 ` Doug Anderson
2014-10-20 19:56 ` Dinh Nguyen
2014-10-20 19:56 ` Dinh Nguyen
2014-10-20 18:41 ` Mark Rutland
2014-10-20 18:41 ` Mark Rutland
2014-10-20 19:04 ` Dinh Nguyen
2014-10-20 19:04 ` Dinh Nguyen
2014-10-20 19:26 ` Doug Anderson
2014-10-20 19:26 ` Doug Anderson
2014-10-20 22:41 ` Mark Rutland
2014-10-20 22:41 ` Mark Rutland
2014-10-20 22:49 ` Jaehoon Chung
2014-10-20 22:49 ` Jaehoon Chung
2014-10-21 0:02 ` Doug Anderson
2014-10-21 0:02 ` Doug Anderson
2014-10-21 9:07 ` Mark Rutland
2014-10-21 9:07 ` Mark Rutland
2014-10-20 15:31 ` [PATCHv2 2/2] ARM: dts: socfpga: Add a 3.3V fixed regulator node dinguyen at opensource.altera.com
2014-10-20 15:31 ` dinguyen
2014-10-20 15:51 ` Doug Anderson
2014-10-20 15:51 ` Doug Anderson
2014-10-20 21:02 ` Dinh Nguyen [this message]
2014-10-20 21:02 ` Dinh Nguyen
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=54457871.404@opensource.altera.com \
--to=dinguyen@opensource.altera.com \
--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 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.