From: Rob Herring <robherring2@gmail.com>
To: Vikas Sajjan <vikas.sajjan@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
l.krishna@samsung.com, devicetree-discuss@lists.ozlabs.org,
joshi@samsung.com, inki.dae@samsung.com,
linaro-kernel@lists.linaro.org, sylvester.nawrocki@gmail.com
Subject: Re: [PATCH] ARM: dts: add interrupt-names property to get interrupt resource by name
Date: Wed, 13 Mar 2013 09:39:53 -0500 [thread overview]
Message-ID: <51408FB9.90808@gmail.com> (raw)
In-Reply-To: <1363173980-11428-1-git-send-email-vikas.sajjan@linaro.org>
The subject is completely misleading. Make it clear what the scope of
this patch is.
On 03/13/2013 06:26 AM, Vikas Sajjan wrote:
> The FIMD driver expects the "vsync" interrupt to be mentioned as the 1st
> parameter in the FIMD DT node. So to meet this expectation of the driver,
> the FIMD DT node was forced to be made by keeping "vsync" as the 1st
> parameter.
>
> this resolves the above mentioned "hack" by introducing
> "interrupt-names", so that FIMD driver can get the interrupt resource by
> name as discussed at
> http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg16211.html
I fail to see what the hack is. The order of interrupt properties must
be defined by the binding. interrupt-names is auxiliary data and must
not be required by an OS.
> patch is dependent on https://patchwork.kernel.org/patch/2184981/
Why the split? These should be combined.
>
> Signed-off-by: Vikas Sajjan <vikas.sajjan@linaro.org>
> ---
> arch/arm/boot/dts/exynos5250.dtsi | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi
> index 0ee4706..76c8911 100644
> --- a/arch/arm/boot/dts/exynos5250.dtsi
> +++ b/arch/arm/boot/dts/exynos5250.dtsi
> @@ -588,6 +588,7 @@
> compatible = "samsung,exynos5-fimd";
> interrupt-parent = <&combiner>;
> reg = <0x14400000 0x40000>;
> - interrupts = <18 5>, <18 4>, <18 6>;
> + interrupt-names = "fifo", "vsync", "lcd_sys";
> + interrupts = <18 4>, <18 5>, <18 6>;
There should be some documentation describing the order of the interrupts.
Rob
next prev parent reply other threads:[~2013-03-13 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 11:26 [PATCH] ARM: dts: add interrupt-names property to get interrupt resource by name Vikas Sajjan
2013-03-13 14:39 ` Rob Herring [this message]
2013-03-13 22:42 ` Sylwester Nawrocki
2013-03-18 15:50 ` Rob Herring
2013-03-18 18:11 ` Stephen Warren
2013-03-18 22:27 ` Rob Herring
2013-03-18 23:00 ` Arnd Bergmann
2013-03-18 23:05 ` Stephen Warren
2013-03-19 22:31 ` Sylwester Nawrocki
2013-03-19 21:40 ` Sylwester Nawrocki
2013-03-20 3:22 ` Vikas Sajjan
2013-03-15 4:04 ` 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=51408FB9.90808@gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=inki.dae@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=l.krishna@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).