From: Tomasz Figa <tomasz.figa@gmail.com>
To: Arun Kumar K <arun.kk@samsung.com>,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org
Cc: kgene.kim@samsung.com, dianders@chromium.org, olofj@google.com,
t.figa@samsung.com, sachin.kamat@linaro.org,
tushar.behera@linaro.org, arunkk.samsung@gmail.com
Subject: Re: [PATCH v3 1/2] ARM: dts: Add node references to 5420
Date: Thu, 01 May 2014 19:25:26 +0200 [thread overview]
Message-ID: <53628386.4090108@gmail.com> (raw)
In-Reply-To: <1398856138-18837-2-git-send-email-arun.kk@samsung.com>
Hi Arun,
Looks mostly fine, just some minor nits to improve readability.
On 30.04.2014 13:08, Arun Kumar K wrote:
> Adding references to nodes which do not have it yet
> in exynos5420.dtsi. This is done so as to use reference
> based node updation in board files.
To stick to correct terminology, the handle that lets you reference a
node is called "label", so this patch adds labels to nodes that don't
have them yet.
>
> Signed-off-by: Arun Kumar K <arun.kk@samsung.com>
> ---
> arch/arm/boot/dts/exynos5420.dtsi | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi
> index c3a9a66..2058276 100644
> --- a/arch/arm/boot/dts/exynos5420.dtsi
> +++ b/arch/arm/boot/dts/exynos5420.dtsi
> @@ -125,7 +125,7 @@
> clock-names = "pll_ref", "pll_in", "sclk_audio", "sclk_pcm_in";
> };
>
> - codec@11000000 {
> + codec: codec@11000000 {
IMHO "mfc" would be a more convenient label.
> compatible = "samsung,mfc-v7";
> reg = <0x11000000 0x10000>;
> interrupts = <0 96 0>;
> @@ -169,7 +169,7 @@
> status = "disabled";
> };
>
> - mct@101C0000 {
> + mct: mct@101C0000 {
> compatible = "samsung,exynos4210-mct";
> reg = <0x101C0000 0x800>;
> interrupt-controller;
> @@ -270,7 +270,7 @@
> interrupts = <0 47 0>;
> };
>
> - rtc@101E0000 {
> + rtc: rtc@101E0000 {
> clocks = <&clock CLK_RTC>;
> clock-names = "rtc";
> status = "disabled";
> @@ -430,22 +430,22 @@
> status = "disabled";
> };
>
> - serial@12C00000 {
> + serial_0: serial@12C00000 {
To match with our hardware naming conventions, uart0 would probably be a
better label. Similarly for remaining serial ports.
With those fixed, feel free to add my Reviewed-by tag.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-05-01 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 11:08 [PATCH v3 0/2] Add peach-pit board support Arun Kumar K
2014-04-30 11:08 ` [PATCH v3 1/2] ARM: dts: Add node references to 5420 Arun Kumar K
[not found] ` <1398856138-18837-2-git-send-email-arun.kk-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-05-01 15:09 ` Doug Anderson
2014-05-01 17:25 ` Tomasz Figa [this message]
2014-05-02 4:16 ` Arun Kumar K
2014-04-30 11:08 ` [PATCH v3 2/2] ARM: dts: Add peach-pit board support Arun Kumar K
2014-05-01 15:40 ` Doug Anderson
2014-05-01 17:30 ` Tomasz Figa
2014-05-01 17:45 ` Doug Anderson
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=53628386.4090108@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=arun.kk@samsung.com \
--cc=arunkk.samsung@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olofj@google.com \
--cc=sachin.kamat@linaro.org \
--cc=t.figa@samsung.com \
--cc=tushar.behera@linaro.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).