From: Tomasz Figa <tomasz.figa@gmail.com>
To: Vikas Sajjan <vikas.sajjan@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
devicetree-discuss@lists.ozlabs.org, jg1.han@samsung.com,
inki.dae@samsung.com, patches@linaro.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 2/7] ARM: dts: Update FIMD DT node for Exynos5 SoCs
Date: Mon, 29 Jul 2013 14:34:53 -0700 (PDT) [thread overview]
Message-ID: <4058541.XvOrGlbWoB@thinkpad> (raw)
In-Reply-To: <1375105771-8106-3-git-send-email-vikas.sajjan@linaro.org>
Hi Vikas,
Please see my comment inline.
On Monday 29 of July 2013 19:19:26 Vikas Sajjan wrote:
> Moves the properties of FIMD DT node which are common across Exynos5 based
> SoCs like Exynos5250 and Exxynos5420 to exynos5.dtsi
>
> Signed-off-by: Vikas Sajjan <vikas.sajjan@linaro.org>
> ---
> arch/arm/boot/dts/exynos5.dtsi | 10 ++++++++++
> arch/arm/boot/dts/exynos5250.dtsi | 6 +-----
> 2 files changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm/boot/dts/exynos5.dtsi b/arch/arm/boot/dts/exynos5.dtsi
> index f65e124..80a4630 100644
> --- a/arch/arm/boot/dts/exynos5.dtsi
> +++ b/arch/arm/boot/dts/exynos5.dtsi
> @@ -108,4 +108,14 @@
> interrupts = <0 42 0>;
> status = "disabled";
> };
> +
> + fimd {
I don't know why this node was named incorrectly in original file (probably the
patch adding it did not have enough review), but if you are modifying it
anyway, could you fix it to be conformant to DT conventions?
Whenever there is a reg property inside a node, the node should be named
whatever@addr, where addr is comma separated list of addresses specified in reg
property, in hex, without "0x" prefix.
So in this case this should be at least
fimd@14400000
but ideally
display-controller@14400000
as nodes should have generic names (see ePAPR, paragraph 2.2.2).
Best regards,
Tomasz
next prev parent reply other threads:[~2013-07-29 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 13:49 [PATCH 0/7] Add DT nodes for FIMD and DP controller for Exynos5420 SoC Vikas Sajjan
2013-07-29 13:49 ` [PATCH 1/7] ARM: dts: Move display-timimg information inside FIMD DT node for exynos5250 Vikas Sajjan
2013-07-29 13:49 ` [PATCH 2/7] ARM: dts: Update FIMD DT node for Exynos5 SoCs Vikas Sajjan
2013-07-29 21:34 ` Tomasz Figa [this message]
2013-07-29 13:49 ` [PATCH 3/7] ARM: dts: Add basic PM domains for EXYNOS5420 Vikas Sajjan
2013-07-29 21:37 ` Tomasz Figa
2013-07-29 13:49 ` [PATCH 4/7] ARM: dts: Add FIMD DT node to exynos5420 DTS files Vikas Sajjan
2013-07-29 21:48 ` Tomasz Figa
2013-07-29 13:49 ` [PATCH 5/7] ARM: dts: Update DP controller DT Node for Exynos5 based SoCs Vikas Sajjan
2013-07-29 13:49 ` [PATCH 6/7] ARM: dts: Add DP controller DT node to exynos5420 SoC Vikas Sajjan
2013-07-29 13:49 ` [PATCH 7/7] ARM: dts: Add pin state information for DP HPD support to Exynos5420 Vikas Sajjan
2013-07-29 21:51 ` [PATCH 0/7] Add DT nodes for FIMD and DP controller for Exynos5420 SoC 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=4058541.XvOrGlbWoB@thinkpad \
--to=tomasz.figa@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=inki.dae@samsung.com \
--cc=jg1.han@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=vikas.sajjan@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 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.