From: Sylwester Nawrocki <sylvester.nawrocki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Leela Krishna Amudala
<l.krishna-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org,
dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cpgs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org
Subject: Re: [PATCH V12 1/3] ARM: dts: Add pmu sysreg node to exynos5250 and exynos5420 dtsi files
Date: Fri, 06 Dec 2013 18:22:32 +0100 [thread overview]
Message-ID: <52A207D8.3030206@gmail.com> (raw)
In-Reply-To: <1386308868-30264-2-git-send-email-l.krishna-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Hi,
Just a few minor comments...
On 12/06/2013 06:47 AM, Leela Krishna Amudala wrote:
> This patch adds pmusysreg node to exynos5250 and exynos5420 dtsi files to
s/pmusysreg/PMU sysreg ? Similarly I would capitalize it in the subject
line as well.
> handle PMU register accesses in a centralized way using syscon driver
>
> Signed-off-by: Leela Krishna Amudala<l.krishna-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> Reviewed-by: Tomasz Figa<t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> Reviewed-by: Doug Anderson<dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> Tested-by: Doug Anderson<dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> ---
> Documentation/devicetree/bindings/arm/samsung/pmu.txt | 15 +++++++++++++++
> arch/arm/boot/dts/exynos5250.dtsi | 5 +++++
> arch/arm/boot/dts/exynos5420.dtsi | 5 +++++
> 3 files changed, 25 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/samsung/pmu.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
> new file mode 100644
> index 0000000..f1f1552
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
I might be easy to confuse this with ARM Performance Monitoring Unit.
So perhaps we should rename this file to, e.g. power-management-unit.txt ?
> @@ -0,0 +1,15 @@
> +SAMSUNG Exynos SoC series PMU Registers
s/PMU/Power Management Unit ?
> +
> +Properties:
> + - compatible : should contain two values. First value must be one from following list:
> + - "samsung,exynos5250-pmu" - for Exynos5250 SoC,
> + - "samsung,exynos5420-pmu" - for Exynos5420 SoC.
s/./; ?
> + second value must be always "syscon".
It might be more safe to specify it as the last value, so something along
the lines of:
The last value should be "syscon".
> +
> + - reg : offset and length of the register set.
> +
> +Example :
> +pmu_system_controller: system-controller@10040000 {
Might be more sensible to use 'power_management_unit' for the label.
> + compatible = "samsung,exynos5250-pmu", "syscon";
> + reg =<0x10040000 0x5000>;
> +};
> diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi
> index b98ffc3..62f9e36 100644
> --- a/arch/arm/boot/dts/exynos5250.dtsi
> +++ b/arch/arm/boot/dts/exynos5250.dtsi
> @@ -163,6 +163,11 @@
> interrupts =<0 47 0>;
> };
>
> + pmu_system_controller: system-controller@10040000 {
s/pmu_system_controller/power_management_unit ? So it describes the
subsystem
better in terms used in the SoCs User Manual ?
> + compatible = "samsung,exynos5250-pmu", "syscon";
> + reg =<0x10040000 0x5000>;
> + };
> +
> watchdog {
> clocks =<&clock 336>;
> clock-names = "watchdog";
> diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi
> index b1fa334..cd47db0 100644
> --- a/arch/arm/boot/dts/exynos5420.dtsi
> +++ b/arch/arm/boot/dts/exynos5420.dtsi
> @@ -402,4 +402,9 @@
> clock-names = "gscl";
> samsung,power-domain =<&gsc_pd>;
> };
> +
> + pmu_system_controller: system-controller@10040000 {
s/pmu_system_controller/power_management_unit ?
> + compatible = "samsung,exynos5420-pmu", "syscon";
> + reg =<0x10040000 0x5000>;
> + };
> };
Otherwise looks good.
Thanks,
Sylwester
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Leela Krishna Amudala <l.krishna@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, wim@iguana.be,
dianders@chromium.org, kgene.kim@samsung.com, t.figa@samsung.com,
devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
cpgs@samsung.com, linux@roeck-us.net
Subject: Re: [PATCH V12 1/3] ARM: dts: Add pmu sysreg node to exynos5250 and exynos5420 dtsi files
Date: Fri, 06 Dec 2013 18:22:32 +0100 [thread overview]
Message-ID: <52A207D8.3030206@gmail.com> (raw)
In-Reply-To: <1386308868-30264-2-git-send-email-l.krishna@samsung.com>
Hi,
Just a few minor comments...
On 12/06/2013 06:47 AM, Leela Krishna Amudala wrote:
> This patch adds pmusysreg node to exynos5250 and exynos5420 dtsi files to
s/pmusysreg/PMU sysreg ? Similarly I would capitalize it in the subject
line as well.
> handle PMU register accesses in a centralized way using syscon driver
>
> Signed-off-by: Leela Krishna Amudala<l.krishna@samsung.com>
> Reviewed-by: Tomasz Figa<t.figa@samsung.com>
> Reviewed-by: Doug Anderson<dianders@chromium.org>
> Tested-by: Doug Anderson<dianders@chromium.org>
> ---
> Documentation/devicetree/bindings/arm/samsung/pmu.txt | 15 +++++++++++++++
> arch/arm/boot/dts/exynos5250.dtsi | 5 +++++
> arch/arm/boot/dts/exynos5420.dtsi | 5 +++++
> 3 files changed, 25 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/samsung/pmu.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
> new file mode 100644
> index 0000000..f1f1552
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
I might be easy to confuse this with ARM Performance Monitoring Unit.
So perhaps we should rename this file to, e.g. power-management-unit.txt ?
> @@ -0,0 +1,15 @@
> +SAMSUNG Exynos SoC series PMU Registers
s/PMU/Power Management Unit ?
> +
> +Properties:
> + - compatible : should contain two values. First value must be one from following list:
> + - "samsung,exynos5250-pmu" - for Exynos5250 SoC,
> + - "samsung,exynos5420-pmu" - for Exynos5420 SoC.
s/./; ?
> + second value must be always "syscon".
It might be more safe to specify it as the last value, so something along
the lines of:
The last value should be "syscon".
> +
> + - reg : offset and length of the register set.
> +
> +Example :
> +pmu_system_controller: system-controller@10040000 {
Might be more sensible to use 'power_management_unit' for the label.
> + compatible = "samsung,exynos5250-pmu", "syscon";
> + reg =<0x10040000 0x5000>;
> +};
> diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi
> index b98ffc3..62f9e36 100644
> --- a/arch/arm/boot/dts/exynos5250.dtsi
> +++ b/arch/arm/boot/dts/exynos5250.dtsi
> @@ -163,6 +163,11 @@
> interrupts =<0 47 0>;
> };
>
> + pmu_system_controller: system-controller@10040000 {
s/pmu_system_controller/power_management_unit ? So it describes the
subsystem
better in terms used in the SoCs User Manual ?
> + compatible = "samsung,exynos5250-pmu", "syscon";
> + reg =<0x10040000 0x5000>;
> + };
> +
> watchdog {
> clocks =<&clock 336>;
> clock-names = "watchdog";
> diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi
> index b1fa334..cd47db0 100644
> --- a/arch/arm/boot/dts/exynos5420.dtsi
> +++ b/arch/arm/boot/dts/exynos5420.dtsi
> @@ -402,4 +402,9 @@
> clock-names = "gscl";
> samsung,power-domain =<&gsc_pd>;
> };
> +
> + pmu_system_controller: system-controller@10040000 {
s/pmu_system_controller/power_management_unit ?
> + compatible = "samsung,exynos5420-pmu", "syscon";
> + reg =<0x10040000 0x5000>;
> + };
> };
Otherwise looks good.
Thanks,
Sylwester
next prev parent reply other threads:[~2013-12-06 17:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 5:47 [PATCH V12 0/3] Add watchdog DT nodes and use syscon regmap interface to configure pmu registers Leela Krishna Amudala
2013-12-06 5:47 ` [PATCH V12 1/3] ARM: dts: Add pmu sysreg node to exynos5250 and exynos5420 dtsi files Leela Krishna Amudala
2013-12-06 16:38 ` Doug Anderson
[not found] ` <1386308868-30264-2-git-send-email-l.krishna-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-12-06 17:22 ` Sylwester Nawrocki [this message]
2013-12-06 17:22 ` Sylwester Nawrocki
2013-12-07 0:57 ` Tomasz Figa
2013-12-07 22:20 ` Sylwester Nawrocki
2013-12-11 12:22 ` Leela Krishna Amudala
2013-12-11 22:57 ` Doug Anderson
2013-12-11 23:57 ` Tomasz Figa
2013-12-12 11:32 ` Leela Krishna Amudala
2013-12-06 19:47 ` Guenter Roeck
2013-12-06 23:01 ` Doug Anderson
2013-12-07 0:48 ` Guenter Roeck
2014-01-10 7:41 ` Wim Van Sebroeck
2014-01-20 4:09 ` Leela Krishna Amudala
2014-01-21 5:08 ` kgene
2013-12-06 5:47 ` [PATCH V12 2/3] watchdog: s3c2410_wdt: use syscon regmap interface to configure pmu register Leela Krishna Amudala
2013-12-06 16:41 ` Doug Anderson
2013-12-06 19:48 ` Guenter Roeck
2014-01-10 7:38 ` Wim Van Sebroeck
2013-12-06 5:47 ` [PATCH V12 3/3] ARM: dts: update watchdog device nodes for Exynos5250 and Exynos5420 Leela Krishna Amudala
2013-12-06 19:48 ` Guenter Roeck
2014-01-20 4:10 ` Leela Krishna Amudala
2013-12-18 12:01 ` [PATCH V12 0/3] Add watchdog DT nodes and use syscon regmap interface to configure pmu registers Leela Krishna Amudala
2014-01-08 11:55 ` Leela Krishna Amudala
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=52A207D8.3030206@gmail.com \
--to=sylvester.nawrocki-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=cpgs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=l.krishna-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=wim-IQzOog9fTRqzQB+pC5nmwQ@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 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.