From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Vikas Sajjan <vikas.sajjan@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
sachin.kamat@linaro.org, t.figa@samsung.com,
devicetree-discuss@lists.ozlabs.org, inki.dae@samsung.com,
jy0922.shim@samsung.com
Subject: Re: [PATCH v6 5/5] ARM: dts: Add FIMD DT binding Documentation
Date: Sun, 03 Mar 2013 21:03:25 +0100 [thread overview]
Message-ID: <5133AC8D.8030401@gmail.com> (raw)
In-Reply-To: <5133A068.7060906@gmail.com>
On 03/03/2013 08:11 PM, Sylwester Nawrocki wrote:
> I have a suggestion here. What about using reg-names property to make this
Oops, this should read "interrupt-names", not "reg-names".
> more explicit, e.g.
>
> - interrupts : should contain a list of all FIMD IP block interrupts:
> FIFO Level, VSYNC, LCD_SYSTEM. The interrupt specifier format depends
> on the interrupt controller used;
>
> - interrupt-names : should contain the interrupt names: "fifo", "vsync",
> "lcd_sys", in the order in which they were listed in the interrupts
> property;
next prev parent reply other threads:[~2013-03-03 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 9:42 [PATCH v6 0/5] Add DRM FIMD DT support for Exynos4 DT Machines Vikas Sajjan
2013-02-28 9:42 ` [PATCH v6 1/5] ARM: dts: Add FIMD node to exynos4 Vikas Sajjan
2013-02-28 9:42 ` [PATCH v6 2/5] ARM: dts: Add lcd pinctrl node entries for EXYNOS4412 SoC Vikas Sajjan
2013-02-28 9:42 ` [PATCH v6 3/5] ARM: dts: Add FIMD node and display timing node to exynos4412-origen.dts Vikas Sajjan
2013-02-28 9:42 ` [PATCH v6 4/5] ARM: dts: Add FIMD AUXDATA node entry for exynos4 DT Vikas Sajjan
2013-02-28 9:42 ` [PATCH v6 5/5] ARM: dts: Add FIMD DT binding Documentation Vikas Sajjan
2013-03-03 19:11 ` Sylwester Nawrocki
2013-03-03 20:03 ` Sylwester Nawrocki [this message]
2013-03-06 10:18 ` Vikas Sajjan
2013-03-06 21:13 ` Sylwester Nawrocki
2013-03-06 21:20 ` Sylwester Nawrocki
2013-03-06 23:56 ` Kukjin Kim
2013-03-07 6:50 ` 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=5133AC8D.8030401@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=inki.dae@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=t.figa@samsung.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).