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, patches@linaro.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 3/3] ARM: dts: Add display timing node to exynos5250-arndale.dts
Date: Fri, 10 May 2013 02:05:42 +0200 [thread overview]
Message-ID: <4212940.hYf2k9NPUY@flatron> (raw)
In-Reply-To: <1367992894-20198-4-git-send-email-vikas.sajjan@linaro.org>
Hi Vikas,
On Wednesday 08 of May 2013 11:31:34 Vikas Sajjan wrote:
> Adds display timing node for a DP panel to Arndale Board DTS file
>
> Signed-off-by: Vikas Sajjan <vikas.sajjan@linaro.org>
> ---
> arch/arm/boot/dts/exynos5250-arndale.dts | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos5250-arndale.dts
> b/arch/arm/boot/dts/exynos5250-arndale.dts index f68b820..c831a5c
> 100644
> --- a/arch/arm/boot/dts/exynos5250-arndale.dts
> +++ b/arch/arm/boot/dts/exynos5250-arndale.dts
> @@ -459,4 +459,20 @@
> samsung,lane-count = <4>;
> };
>
> + display-timings {
> + native-mode = <&timing0>;
> + timing0: timing@0 {
> + /* 2560x1600 DP panel */
> + clock-frequency = <50000>;
> + hactive = <2560>;
> + vactive = <1600>;
> + hfront-porch = <48>;
> + hback-porch = <80>;
> + hsync-len = <32>;
> + vback-porch = <16>;
> + vfront-porch = <8>;
> + vsync-len = <6>;
> + };
> + };
What display are those timings used for? Shouldn't they be placed inside
node of that display?
Best regards,
Tomasz
next prev parent reply other threads:[~2013-05-10 0:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 6:01 [PATCH 0/3] Add DP related DT and Display-timing Node to exynos5250 based Arndale Board Vikas Sajjan
2013-05-08 6:01 ` [PATCH 1/3] ARM: dts: Add DT node for DP controller for " Vikas Sajjan
2013-05-13 1:20 ` Jingoo Han
2013-06-05 11:26 ` Kukjin Kim
2013-06-05 11:43 ` Kukjin Kim
2013-05-08 6:01 ` [PATCH 2/3] ARM: dts: Add clock provider information for DP controller in Exynos5250 SoC Vikas Sajjan
2013-05-13 1:21 ` Jingoo Han
2013-06-05 11:25 ` Kukjin Kim
2013-05-08 6:01 ` [PATCH 3/3] ARM: dts: Add display timing node to exynos5250-arndale.dts Vikas Sajjan
2013-05-10 0:05 ` Tomasz Figa [this message]
2013-05-10 2:55 ` Vikas Sajjan
[not found] ` <CAD025yRnuk2oK1B40p5XTQ7n+aX+ta2PTdEuceCbvRUEvRgzSg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-10 3:58 ` Vikas Sajjan
2013-05-10 5:38 ` Olof Johansson
[not found] ` <CAOesGMg0LLhC7=EYtWxaDL5x=v=ZA6ov5K_j-nxhzev4L-w-Rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-10 6:21 ` Vikas Sajjan
[not found] ` <CAD025yQ+vnNc1RqoqoBw9JqYUp6aAY2wTowhVyV+zoDZq9sJ6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-10 6:27 ` Vikas Sajjan
2013-05-10 7:33 ` Tomasz Figa
2013-05-10 8:15 ` Vikas Sajjan
[not found] ` <CAD025ySqUpGRpx0J61gsjKE_JPa+Mu444ETpd2USyikrNWj71w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-14 13:10 ` Vikas Sajjan
2013-05-14 13:25 ` Steffen Trumtrar
[not found] ` <20130514132523.GA10292-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-05-14 13:39 ` 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=4212940.hYf2k9NPUY@flatron \
--to=tomasz.figa@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox