devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	kernel@collabora.com,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/1] ARM: dts: imx53: PPD: Add fixed-regulator information
Date: Sat, 23 Jun 2018 13:00:17 -0300	[thread overview]
Message-ID: <CAOMZO5Bdh9d6nrX80xpkmFdFydfmazSkU+bwzNGFQFGz8dPAPA@mail.gmail.com> (raw)
In-Reply-To: <20180622145225.17883-1-sebastian.reichel@collabora.co.uk>

Hi Sebastian,

On Fri, Jun 22, 2018 at 11:52 AM, Sebastian Reichel
<sebastian.reichel@collabora.co.uk> wrote:

> -       usbphy2: usbphy2 {
> +       usbphy2: usbphy-2 {

This node rename seems to be an unrelated change.

>                 compatible = "usb-nop-xceiv";
> +               vcc-supply = <&reg_3v3>;
>                 reset-gpios = <&gpio4 4 GPIO_ACTIVE_LOW>;
>                 clock-names = "main_clk";
>                 clock-frequency = <24000000>;
> @@ -208,8 +230,9 @@
>                 assigned-clock-parents = <&clks IMX5_CLK_OSC>;
>         };
>
> -       usbphy3: usbphy3 {
> +       usbphy3: usbphy-3 {

Ditto.

      reply	other threads:[~2018-06-23 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 14:52 [PATCH 1/1] ARM: dts: imx53: PPD: Add fixed-regulator information Sebastian Reichel
2018-06-23 16:00 ` Fabio Estevam [this message]

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=CAOMZO5Bdh9d6nrX80xpkmFdFydfmazSkU+bwzNGFQFGz8dPAPA@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@collabora.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sebastian.reichel@collabora.co.uk \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).