devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Kamat <sachin.kamat@linaro.org>
To: Vikas Sajjan <vikas.sajjan@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
	sylvester.nawrocki@gmail.com,
	devicetree-discuss@lists.ozlabs.org, inki.dae@samsung.com,
	linaro-kernel@lists.linaro.org, joshi@samsung.com
Subject: Re: [PATCH v8 4/4] ARM: dts: Add FIMD DT binding Documentation
Date: Tue, 19 Mar 2013 13:31:16 +0530	[thread overview]
Message-ID: <CAK9yfHwzeMcHOTRWg_HF+aagPdqyeHADNPDJj4Dj0QnH8Fmjig@mail.gmail.com> (raw)
In-Reply-To: <1363676892-21296-5-git-send-email-vikas.sajjan@linaro.org>

Hi Vikas,

> +Example:
> +
> +SoC specific DT Entry:
> +
> +       fimd@11c00000 {
> +               compatible = "samsung,exynos4210-fimd";
> +               interrupt-parent = <&combiner>;
> +               reg = <0x11c00000 0x20000>;
> +               interrupt-names = "fifo", "vsync", "lcd_sys";
> +               interrupts = <11 0>, <11 1>, <11 2>;
> +               clocks = <&clock 140>, <&clock 283>;
> +               clock-names = "sclk_fimd", "fimd";

Now that you have added clock properties, you need to make a mention
about them too in the description above.

-- 
With warm regards,
Sachin

  reply	other threads:[~2013-03-19  8:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19  7:08 [PATCH v8 0/4] Add DRM FIMD DT support for Exynos4 DT Machines Vikas Sajjan
2013-03-19  7:08 ` [PATCH v8 1/4] ARM: dts: Add FIMD node to exynos4 Vikas Sajjan
2013-03-19  7:08 ` [PATCH v8 2/4] ARM: dts: Add lcd pinctrl node entries for EXYNOS4412 SoC Vikas Sajjan
2013-03-19  7:08 ` [PATCH v8 3/4] ARM: dts: Add FIMD node and display timing node to exynos4412-origen.dts Vikas Sajjan
2013-03-19  7:08 ` [PATCH v8 4/4] ARM: dts: Add FIMD DT binding Documentation Vikas Sajjan
2013-03-19  8:01   ` Sachin Kamat [this message]
2013-03-21  4:45 ` [PATCH v8 0/4] Add DRM FIMD DT support for Exynos4 DT Machines Vikas Sajjan

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=CAK9yfHwzeMcHOTRWg_HF+aagPdqyeHADNPDJj4Dj0QnH8Fmjig@mail.gmail.com \
    --to=sachin.kamat@linaro.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=inki.dae@samsung.com \
    --cc=joshi@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=sylvester.nawrocki@gmail.com \
    --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 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).