From: Leela Krishna Amudala <l.krishna@samsung.com>
To: linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
ben-linux@fluff.org, kgene.kim@samsung.com,
m.szyprowski@samsung.com
Subject: [PATCH V3 2/5] include/video: Add Exynos5 specific FIMD register offsets
Date: Tue, 07 Aug 2012 09:49:56 +0000 [thread overview]
Message-ID: <1344332279-16736-3-git-send-email-l.krishna@samsung.com> (raw)
In-Reply-To: <1344332279-16736-1-git-send-email-l.krishna@samsung.com>
Exynos5 has VIDTCON and VIDCON registers at different offsets
from the previous SOCs. Hence, adding the macros.
Signed-off-by: Leela Krishna Amudala <l.krishna@samsung.com>
---
include/video/samsung_fimd.h | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/include/video/samsung_fimd.h b/include/video/samsung_fimd.h
index e979f42..7ae6c07 100644
--- a/include/video/samsung_fimd.h
+++ b/include/video/samsung_fimd.h
@@ -524,3 +524,10 @@
* 1110 -none- -none- -none- -none- -none-
* 1111 -none- -none- -none- -none- -none-
*/
+
+/* FIMD Version 8 register offset definitions */
+#define FIMD_V8_VIDTCON0 (0x20010)
+#define FIMD_V8_VIDTCON1 (0x20014)
+#define FIMD_V8_VIDTCON2 (0x20018)
+#define FIMD_V8_VIDTCON3 (0x2001C)
+#define FIMD_V8_VIDCON1 (0x20004)
--
1.7.0.4
next prev parent reply other threads:[~2012-08-07 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 9:49 [PATCH V3 0/5] arm: samsung: Move FIMD headers to include/video/ Leela Krishna Amudala
2012-08-07 9:49 ` [PATCH V3 1/5] include/video: Add samsung FIMD register header Leela Krishna Amudala
2012-08-07 9:49 ` Leela Krishna Amudala [this message]
2012-08-07 9:49 ` [PATCH V3 3/5] arm: samsung: Include the modified FIMD header file Leela Krishna Amudala
2012-08-07 9:49 ` [PATCH V3 4/5] driver: " Leela Krishna Amudala
2012-08-07 9:49 ` [PATCH V3 5/5] arm: samsung: delete frame buffer header files from platform Leela Krishna Amudala
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=1344332279-16736-3-git-send-email-l.krishna@samsung.com \
--to=l.krishna@samsung.com \
--cc=ben-linux@fluff.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.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;
as well as URLs for NNTP newsgroup(s).