From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 1/2] ARM: davinci: dm365: add support for v4l2 video display
Date: Tue, 9 Apr 2013 17:18:20 +0530 [thread overview]
Message-ID: <51640004.6020604@ti.com> (raw)
In-Reply-To: <1365412636-3468-2-git-send-email-prabhakar.csengg@gmail.com>
On 4/8/2013 2:47 PM, Prabhakar lad wrote:
> From: Lad, Prabhakar <prabhakar.csengg@gmail.com>
>
> Create platform devices for various video modules like venc,osd,
> vpbe and v4l2 driver for dm365.
>
> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> Acked-by: Sekhar Nori <nsekhar@ti.com>
> ---
> diff --git a/arch/arm/mach-davinci/davinci.h b/arch/arm/mach-davinci/davinci.h
> index 12d544b..a9de512 100644
> --- a/arch/arm/mach-davinci/davinci.h
> +++ b/arch/arm/mach-davinci/davinci.h
> @@ -36,8 +36,13 @@
> #include <media/davinci/vpbe_osd.h>
>
> #define DAVINCI_SYSTEM_MODULE_BASE 0x01c40000
> +#define SYSMOD_VDAC_CONFIG 0x2c
> #define SYSMOD_VIDCLKCTL 0x38
> #define SYSMOD_VPSS_CLKCTL 0x44
> +#define VPSS_VENCCLKEN_ENABLE BIT(3)
> +#define VPSS_DACCLKEN_ENABLE BIT(4)
> +#define VPSS_PLLC2SYSCLK5_ENABLE BIT(5)
> +
Prabhakar, I noticed it only after I applied these patches, but these
bit definitions in between list of register offsets is distracting. Can
you please move them down after the register offsets when you send the
pull request? You can add a comment /* VPSS CLKCTL bit definitions */
before you start the bit definitions.
> #define SYSMOD_VDD3P3VPWDN 0x48
> #define SYSMOD_VSCLKDIS 0x6c
> #define SYSMOD_PUPDCTL1 0x7c
Thanks,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: Sekhar Nori <nsekhar@ti.com>
To: Prabhakar lad <prabhakar.csengg@gmail.com>
Cc: DLOS <davinci-linux-open-source@linux.davincidsp.com>,
LAK <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v9 1/2] ARM: davinci: dm365: add support for v4l2 video display
Date: Tue, 9 Apr 2013 17:18:20 +0530 [thread overview]
Message-ID: <51640004.6020604@ti.com> (raw)
In-Reply-To: <1365412636-3468-2-git-send-email-prabhakar.csengg@gmail.com>
On 4/8/2013 2:47 PM, Prabhakar lad wrote:
> From: Lad, Prabhakar <prabhakar.csengg@gmail.com>
>
> Create platform devices for various video modules like venc,osd,
> vpbe and v4l2 driver for dm365.
>
> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> Acked-by: Sekhar Nori <nsekhar@ti.com>
> ---
> diff --git a/arch/arm/mach-davinci/davinci.h b/arch/arm/mach-davinci/davinci.h
> index 12d544b..a9de512 100644
> --- a/arch/arm/mach-davinci/davinci.h
> +++ b/arch/arm/mach-davinci/davinci.h
> @@ -36,8 +36,13 @@
> #include <media/davinci/vpbe_osd.h>
>
> #define DAVINCI_SYSTEM_MODULE_BASE 0x01c40000
> +#define SYSMOD_VDAC_CONFIG 0x2c
> #define SYSMOD_VIDCLKCTL 0x38
> #define SYSMOD_VPSS_CLKCTL 0x44
> +#define VPSS_VENCCLKEN_ENABLE BIT(3)
> +#define VPSS_DACCLKEN_ENABLE BIT(4)
> +#define VPSS_PLLC2SYSCLK5_ENABLE BIT(5)
> +
Prabhakar, I noticed it only after I applied these patches, but these
bit definitions in between list of register offsets is distracting. Can
you please move them down after the register offsets when you send the
pull request? You can add a comment /* VPSS CLKCTL bit definitions */
before you start the bit definitions.
> #define SYSMOD_VDD3P3VPWDN 0x48
> #define SYSMOD_VSCLKDIS 0x6c
> #define SYSMOD_PUPDCTL1 0x7c
Thanks,
Sekhar
next prev parent reply other threads:[~2013-04-09 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:17 [PATCH v9 0/2] ARM: davinci: add support for dm365 vpbe display Prabhakar lad
2013-04-08 9:17 ` Prabhakar lad
2013-04-08 9:17 ` [PATCH v9 1/2] ARM: davinci: dm365: add support for v4l2 video display Prabhakar lad
2013-04-08 9:17 ` Prabhakar lad
2013-04-09 11:48 ` Sekhar Nori [this message]
2013-04-09 11:48 ` Sekhar Nori
2013-04-09 11:51 ` Prabhakar Lad
2013-04-09 11:51 ` Prabhakar Lad
2013-04-09 23:49 ` Greg Veintimilla
2013-04-09 23:49 ` Greg Veintimilla
2013-04-08 9:17 ` [PATCH v9 2/2] ARM: davinci: dm365 EVM: add support for VPBE display Prabhakar lad
2013-04-08 9:17 ` Prabhakar lad
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=51640004.6020604@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.