From: Sergei Shtylyov <sshtylyov@mvista.com>
To: "Hadli, Manjunath" <manjunath.hadli@ti.com>
Cc: LMML <linux-media@vger.kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
dlos <davinci-linux-open-source@linux.davincidsp.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [PATCH v14 1/2] davinci vpbe: platform specific additions
Date: Mon, 17 Jan 2011 18:22:22 +0300 [thread overview]
Message-ID: <4D345EAE.3040303@mvista.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930247F9A823@dbde02.ent.ti.com>
Hello.
Hadli, Manjunath wrote:
>>> This patch implements the overall device creation for the Video
>>> display driver.
>> It does not only that...
>>> Signed-off-by: Manjunath Hadli<manjunath.hadli@ti.com>
>>> Acked-by: Muralidharan Karicheri<m-karicheri2@ti.com>
>>> Acked-by: Hans Verkuil<hverkuil@xs4all.nl>
>> [...]
>>> diff --git a/arch/arm/mach-davinci/devices.c
>>> b/arch/arm/mach-davinci/devices.c index 22ebc64..f435c7d 100644
>>> --- a/arch/arm/mach-davinci/devices.c
>>> +++ b/arch/arm/mach-davinci/devices.c
>>> @@ -33,6 +33,8 @@
>>> #define DM365_MMCSD0_BASE 0x01D11000
>>> #define DM365_MMCSD1_BASE 0x01D00000
>>>
>>> +void __iomem *davinci_sysmodbase;
>>> +
>> I think this should be added in a sperate patch.
I meant to type "separate". :-)
>>> diff --git a/arch/arm/mach-davinci/include/mach/dm644x.h
>>> b/arch/arm/mach-davinci/include/mach/dm644x.h
>>> index 5a1b26d..790925f 100644
>>> --- a/arch/arm/mach-davinci/include/mach/dm644x.h
>>> +++ b/arch/arm/mach-davinci/include/mach/dm644x.h
>>> @@ -40,8 +44,14 @@
>>> #define DM644X_ASYNC_EMIF_DATA_CE2_BASE 0x06000000
>>> #define DM644X_ASYNC_EMIF_DATA_CE3_BASE 0x08000000
>>>
>>> +/* VPBE register base addresses */
>>> +#define DM644X_VPSS_REG_BASE 0x01c73400
>>> +#define DM644X_VENC_REG_BASE 0x01C72400
>>> +#define DM644X_OSD_REG_BASE 0x01C72600
>> Note that for other devices we don't have '_REG' in such macros. Would make sense to delete it here for consistency.
> You mean other devices like Dm355/Dm365?
No, I mean macros defining the base addresses of the other SoC devices (like
EMAC and AEMIF you have just above your macros).
WBR, Sergei
prev parent reply other threads:[~2011-01-17 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 13:31 [PATCH v14 1/2] davinci vpbe: platform specific additions Manjunath Hadli
2011-01-15 15:43 ` Sergei Shtylyov
2011-01-17 14:04 ` Hadli, Manjunath
2011-01-17 15:22 ` Sergei Shtylyov [this message]
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=4D345EAE.3040303@mvista.com \
--to=sshtylyov@mvista.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-media@vger.kernel.org \
--cc=manjunath.hadli@ti.com \
--cc=mchehab@redhat.com \
/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