From: Chanho Park <chanho61.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: 'Kukjin Kim' <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
'Tomasz Figa' <t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
k.debski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org
Subject: RE: [PATCHv4 1/4] ARM: dts: exynos4: add PMU syscon node
Date: Tue, 20 May 2014 11:01:59 +0900 [thread overview]
Message-ID: <011801cf73cf$7c5fc770$751f5650$@samsung.com> (raw)
In-Reply-To: <537A2FEA.6070208-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Hi Kukjin,
> -----Original Message-----
> From: Kukjin Kim [mailto:kgene.kim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org] On Behalf Of Kukjin Kim
> Sent: Tuesday, May 20, 2014 1:23 AM
> To: Tomasz Figa
> Cc: Chanho Park; kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org; linux-samsung-
> soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; k.debski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org
> Subject: Re: [PATCHv4 1/4] ARM: dts: exynos4: add PMU syscon node
>
> On 05/16/14 02:07, Tomasz Figa wrote:
> > Hi Chanho,
> >
> Hi,
>
> > When testing some other patches with this series applied I found one
> > more issue. Please see below.
> >
> > On 02.05.2014 06:26, Chanho Park wrote:
> >> This patch adds a PMU(Power Management Unit) syscon node. This
> >> should be required for USB Phy syscon regmap I/F.
> >>
> >> Cc: Kamil Debski<k.debski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> >> Signed-off-by: Chanho Park<chanho61.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> >> Reviewed-by: Tomasz Figa<t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> >> ---
> >> Documentation/devicetree/bindings/arm/samsung/pmu.txt | 3 +++
> >> arch/arm/boot/dts/exynos4.dtsi | 5 +++++
> >> arch/arm/boot/dts/exynos4x12.dtsi | 4 ++++
> >> 3 files changed, 12 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt
> b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
> >> index f1f1552..b562634 100644
> >> --- a/Documentation/devicetree/bindings/arm/samsung/pmu.txt
> >> +++ b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
> >> @@ -2,6 +2,9 @@ SAMSUNG Exynos SoC series PMU Registers
> >>
> >> Properties:
> >> - compatible : should contain two values. First value must be one
> from following list:
> >> + - "samsung,exynos4210-pmu" - for Exynos4210 SoC,
> >> + - "samsung,exynos4212-pmu" - for Exynos4212 SoC,
> >> + - "samsung,exynos4412-pmu" - for Exynos4412 SoC,
> >
> > Here two compatible strings are specified, one for each SoC in 4x12
> > family, but...
> >
> >> - "samsung,exynos5250-pmu" - for Exynos5250 SoC,
> >> - "samsung,exynos5420-pmu" - for Exynos5420 SoC.
> >> second value must be always "syscon".
> >> diff --git a/arch/arm/boot/dts/exynos4.dtsi
> b/arch/arm/boot/dts/exynos4.dtsi
> >> index 2f8bcd0..264066f 100644
> >> --- a/arch/arm/boot/dts/exynos4.dtsi
> >> +++ b/arch/arm/boot/dts/exynos4.dtsi
> >> @@ -110,6 +110,11 @@
> >> reg =<0x10010000 0x400>;
> >> };
> >>
> >> + pmu_system_controller: system-controller@10020000 {
> >> + compatible = "samsung,exynos4210-pmu", "syscon";
> >> + reg =<0x10020000 0x4000>;
> >> + };
> >> +
> >> dsi_0: dsi@11C80000 {
> >> compatible = "samsung,exynos4210-mipi-dsi";
> >> reg =<0x11C80000 0x10000>;
> >> diff --git a/arch/arm/boot/dts/exynos4x12.dtsi
> b/arch/arm/boot/dts/exynos4x12.dtsi
> >> index c4a9306..7f767f7 100644
> >> --- a/arch/arm/boot/dts/exynos4x12.dtsi
> >> +++ b/arch/arm/boot/dts/exynos4x12.dtsi
> >> @@ -119,6 +119,10 @@
> >> interrupts =<0 72 0>;
> >> };
> >>
> >> + pmu_system_controller: system-controller@10020000 {
> >> + compatible = "samsung,exynos4x12-pmu", "syscon";
> >
> > Here one node is added for both using an undocumented compatible
> string.
> > Please fix this according to documentation.
> >
>
> Chanho, updated patch?
I'll re-send the patchset soon.
Thanks.
Best Regards,
Chanho Park
--
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-05-20 2:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 4:26 [PATCHv4 0/4] Enable usbphy and hsotg for exynos4 Chanho Park
2014-05-02 4:26 ` [PATCHv4 1/4] ARM: dts: exynos4: add PMU syscon node Chanho Park
2014-05-15 17:07 ` Tomasz Figa
2014-05-19 16:23 ` Kukjin Kim
[not found] ` <537A2FEA.6070208-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-05-20 2:01 ` Chanho Park [this message]
2014-05-20 2:01 ` Chanho Park
2014-05-02 4:26 ` [PATCHv4 2/4] ARM: dts: exynos4: add exynos_usbphy node Chanho Park
2014-05-02 4:26 ` [PATCHv4 3/4] ARM: dts: exynos4: add hsotg device node Chanho Park
2014-05-02 4:26 ` [PATCHv4 4/4] ARM: dts: exynos4412-trats2: enable usb nodes Chanho Park
2014-05-02 18:21 ` [PATCHv4 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='011801cf73cf$7c5fc770$751f5650$@samsung.com' \
--to=chanho61.park-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=k.debski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.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