Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Chanho Park <chanho61.park@samsung.com>
To: 'Sachin Kamat' <sachin.kamat@linaro.org>
Cc: 'Kukjin Kim' <kgene.kim@samsung.com>,
	'linux-samsung-soc' <linux-samsung-soc@vger.kernel.org>,
	'Tomasz Figa' <t.figa@samsung.com>,
	'Kamil Debski' <k.debski@samsung.com>,
	devicetree@vger.kernel.org
Subject: RE: [PATCHv2 2/4] ARM: dts: exynos4: add exynos_usbphy node
Date: Tue, 29 Apr 2014 19:21:10 +0900	[thread overview]
Message-ID: <012c01cf6394$bdb4dc10$391e9430$@samsung.com> (raw)
In-Reply-To: <CAK9yfHx-m0+znU+pt7emqNtop4Y4wKEOcCQBXmw2akusavtUzA@mail.gmail.com>

Hi Sachin,

> -----Original Message-----
> From: Sachin Kamat [mailto:sachin.kamat@linaro.org]
> Sent: Tuesday, April 29, 2014 6:23 PM
> To: Chanho Park
> Cc: Kukjin Kim; linux-samsung-soc; Tomasz Figa; Kamil Debski;
> devicetree@vger.kernel.org
> Subject: Re: [PATCHv2 2/4] ARM: dts: exynos4: add exynos_usbphy node
> 
> Hi Chanho,
> 
> On 25 April 2014 12:29, Chanho Park <chanho61.park@samsung.com> wrote:
> > This patch enables a exynos_usbphy node for exynos4 SoCs.
> > A exynos4x12 usb phy node is almost same with 4210's one
> > except compatible string and pmu syscon.
> >
> > Cc: Tomasz Figa <t.figa@samsung.com>
> > Cc: Kamil Debski <k.debski@samsung.com>
> > Signed-off-by: Chanho Park <chanho61.park@samsung.com>
> > ---
> >  arch/arm/boot/dts/exynos4.dtsi    | 10 ++++++++++
> >  arch/arm/boot/dts/exynos4x12.dtsi |  5 +++++
> >  2 files changed, 15 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/exynos4.dtsi
> b/arch/arm/boot/dts/exynos4.dtsi
> > index 264066f..5f9b23b 100644
> > --- a/arch/arm/boot/dts/exynos4.dtsi
> > +++ b/arch/arm/boot/dts/exynos4.dtsi
> > @@ -278,6 +278,16 @@
> >                 status = "disabled";
> >         };
> >
> > +       exynos_usbphy: exynos-usbphy@125B0000 {
> > +               compatible = "samsung,exynos4210-usb2-phy";
> > +               reg = <0x125B0000 0x100>;
> > +               samsung,pmureg-phandle = <&pmu_system_controller>;
> > +               clocks = <&clock CLK_USB_DEVICE>, <&clock CLK_XUSBXTI>;
> > +               clock-names = "phy", "ref";
> > +               status = "disabled";
> 
> For readability it is better if status line is the last entry of the
> node.

Yes. It could be more readable it is in the last line. I'll update it in next patch.
Thanks.

Best Regards,
Chanho Park

  reply	other threads:[~2014-04-29 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  6:59 [PATCHv2 0/4] Enable usbphy and hsotg for exynos4 Chanho Park
2014-04-25  6:59 ` [PATCHv2 1/4] ARM: dts: exynos4: add PMU syscon node Chanho Park
2014-04-25 23:55   ` Tomasz Figa
2014-04-25  6:59 ` [PATCHv2 2/4] ARM: dts: exynos4: add exynos_usbphy node Chanho Park
2014-04-29  9:23   ` Sachin Kamat
2014-04-29 10:21     ` Chanho Park [this message]
2014-04-25  6:59 ` [PATCHv2 3/4] ARM: dts: exynos4: add hsotg device node Chanho Park
2014-04-25  6:59 ` [PATCHv2 4/4] ARM: dts: exynos4412-trats2: enable usb nodes Chanho Park
2014-04-25  9:03 ` [PATCHv2 0/4] Enable usbphy and hsotg for exynos4 Tomasz Figa

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='012c01cf6394$bdb4dc10$391e9430$@samsung.com' \
    --to=chanho61.park@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=k.debski@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=sachin.kamat@linaro.org \
    --cc=t.figa@samsung.com \
    /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