From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/2] ARM: dts: imx6q: add Novena board
Date: Fri, 11 Dec 2015 19:07:00 +0800 [thread overview]
Message-ID: <20151211110700.GD11252@tiger> (raw)
In-Reply-To: <201512021641.31222.marex@denx.de>
On Wed, Dec 02, 2015 at 04:41:31PM +0100, Marek Vasut wrote:
> On Wednesday, December 02, 2015 at 08:53:05 AM, Shawn Guo wrote:
> > On Sat, Nov 28, 2015 at 03:47:04PM +0100, Marek Vasut wrote:
> > > + reg_usb_otg_vbus: usb_otg_vbus {
> > > + compatible = "regulator-fixed";
> > > + regulator-name = "usb_otg_vbus";
> > > + regulator-min-microvolt = <5000000>;
> > > + regulator-max-microvolt = <5000000>;
> > > + enable-active-high;
> > > + };
> >
> > All these regulator nodes are named so arbitrarily. Can we name them a
> > bit consistently, something like regulator-xxx?
>
> All of them are named like this (well, but the otg_vbus, I can fix that)
>
> reg_something: something-regulator {}
>
> What do you want to see here ?
reg_something: regulator-something {}
Shawn
next prev parent reply other threads:[~2015-12-11 11:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 14:47 [PATCH V2 1/2] devicetree: bindings: Add vendor prefix for Kosagi Marek Vasut
2015-11-28 14:47 ` [PATCH V3 2/2] ARM: dts: imx6q: add Novena board Marek Vasut
2015-11-30 10:19 ` Lucas Stach
2015-11-30 12:21 ` Marek Vasut
2015-11-30 10:57 ` Fabio Estevam
2015-12-02 7:53 ` Shawn Guo
2015-12-02 15:41 ` Marek Vasut
2015-12-11 11:07 ` Shawn Guo [this message]
2015-12-12 3:25 ` Marek Vasut
2015-12-12 3:27 ` [PATCH V4 " Marek Vasut
2015-12-14 1:38 ` Shawn Guo
2015-12-14 3:56 ` Marek Vasut
2015-12-14 13:53 ` Sergei Shtylyov
2015-12-14 14:12 ` Marek Vasut
2015-12-14 14:17 ` Fabio Estevam
2015-12-14 14:41 ` Marek Vasut
2015-12-14 14:45 ` Fabio Estevam
2015-12-14 14:47 ` Marek Vasut
2015-12-15 3:33 ` Marek Vasut
2015-12-14 1:36 ` [PATCH V2 1/2] devicetree: bindings: Add vendor prefix for Kosagi Shawn Guo
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=20151211110700.GD11252@tiger \
--to=shawnguo@kernel.org \
--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.