From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/2] ARM: davinci: dm365 EVM: add support for VPBE display
Date: Tue, 4 Dec 2012 18:52:45 +0530 [thread overview]
Message-ID: <50BDF925.3090700@ti.com> (raw)
In-Reply-To: <1354522904-22501-3-git-send-email-prabhakar.lad@ti.com>
On 12/3/2012 1:51 PM, Prabhakar Lad wrote:
> From: Manjunath Hadli <manjunath.hadli@ti.com>
>
> add support for V4L2 video display to DM365 EVM.
> Support for SD and ED modes is provided, along with Composite
> and Component outputs.
>
> Signed-off-by: Manjunath Hadli <manjunath.hadli@ti.com>
> Signed-off-by: Lad, Prabhakar <prabhakar.lad@ti.com>
> ---
> arch/arm/mach-davinci/board-dm365-evm.c | 177 ++++++++++++++++++++++++++++++-
> 1 files changed, 176 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-davinci/board-dm365-evm.c b/arch/arm/mach-davinci/board-dm365-evm.c
> index 0c3dae6..10f2a85 100644
> --- a/arch/arm/mach-davinci/board-dm365-evm.c
> +++ b/arch/arm/mach-davinci/board-dm365-evm.c
> @@ -27,6 +27,7 @@
> #include <linux/input.h>
> #include <linux/spi/spi.h>
> #include <linux/spi/eeprom.h>
> +#include <linux/v4l2-dv-timings.h>
>
> #include <asm/mach-types.h>
> #include <asm/mach/arch.h>
> @@ -374,6 +375,180 @@ static struct vpfe_config vpfe_cfg = {
> .ccdc = "ISIF",
> };
>
> +/* venc standards timings */
> +static struct vpbe_enc_mode_info dm365evm_enc_std_timing[] = {
> + {
> + .name = "ntsc",
> + .timings_type = VPBE_ENC_STD,
> + .std_id = V4L2_STD_525_60,
> + .interlaced = 1,
> + .xres = 720,
> + .yres = 480,
> + .aspect = {11, 10},
> + .fps = {30000, 1001},
> + .left_margin = 0x79,
> + .right_margin = 0,
> + .upper_margin = 0x10,
> + .lower_margin = 0,
> + .hsync_len = 0,
> + .vsync_len = 0,
> + .flags = 0,
I wonder what makes this entire information board specific? Shouldn't
these (or at least most of these) be same across all devices which
support NTSC and hence should be coming from some common code instead of
being replicated for each platform that supports NTSC?
Thanks,
Sekhar
next prev parent reply other threads:[~2012-12-04 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 8:21 [PATCH v5 0/2] ARM: davinci: add support for dm365 vpbe display Prabhakar Lad
2012-12-03 8:21 ` [PATCH v5 1/2] ARM: davinci: dm365: add support for v4l2 video display Prabhakar Lad
2012-12-04 13:14 ` Sekhar Nori
2012-12-18 17:27 ` Prabhakar Lad
2012-12-03 8:21 ` [PATCH v5 2/2] ARM: davinci: dm365 EVM: add support for VPBE display Prabhakar Lad
2012-12-04 13:22 ` Sekhar Nori [this message]
2013-03-14 8:39 ` Prabhakar Lad
2013-03-14 8:58 ` Sekhar Nori
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=50BDF925.3090700@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).