From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fwd: TI:OMAP: [PATCH 5/7] Add DSS driver for OMAP3
Date: Mon, 25 Jan 2010 08:46:23 -0600 [thread overview]
Message-ID: <4B5DAEBF.2010300@windriver.com> (raw)
In-Reply-To: <a8ca84ad1001250605h9dc1237k990ca21c5e6bed9d@mail.gmail.com>
Khasim Syed Mohammed wrote:
> On Sun, Jan 24, 2010 at 5:48 AM, Tom <Tom.Rix@windriver.com> wrote:
>> Khasim Syed Mohammed wrote:
>>> From cf8fa28973de7609d27146730d9e019b7c919b51 Mon Sep 17 00:00:00 2001
>>> From: Syed Mohammed Khasim <khasim@ti.com>
>>> Date: Tue, 12 Jan 2010 23:57:28 +0530
>>> Subject: [PATCH] Add DSS driver for OMAP3
>>>
>>> Supports dynamic panel configuration
>>> Supports dynamic tv standard selection
>>> Adds support for DSS register access through generic APIs
>>>
>>> Incorporated DSS register access using structures.
>>>
>>> Previous discussions are here
>>> http://www.mail-archive.com/u-boot at lists.denx.de/msg27150.html
>>>
>>> Signed-off-by: Syed Mohammed Khasim <khasim@ti.com>
>>> ---
>>> drivers/video/Makefile | 1 +
>>> drivers/video/omap3_dss.c | 130 ++++++++++++++++++++++++++++
>>> include/asm-arm/arch-omap3/dss.h | 173
>>> ++++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 304 insertions(+), 0 deletions(-)
>>> create mode 100644 drivers/video/omap3_dss.c
>>> create mode 100644 include/asm-arm/arch-omap3/dss.h
>>>
<snip>
>>> +/*
>>> + * DSS Base Registers
>>> + */
>>> +#define OMAP3_DSS_BASE 0x48050040
>>> +#define OMAP3_DISPC_BASE 0x48050440
>>> +#define OMAP3_VENC_BASE 0x48050C00
>>> +
>>> +/* DSS Registers */
>>> +struct dss_regs {
>>> + u32 control; /* 0x40 */
>> Add a comment to explain why base starts at 0x40
>> could also be handled with changing code
>> OMAP3_DSS_BASE 0x48050000
>> struct dss_regs {
>> u8 reserved_1[0x40];
>> ..
> may be,.. let me try.
This can just be fixed by a simple comment like
/* Note : 0x40 is offset from OMAP3_DSS_BASE */
This helps avoid people wondering why 0x40 and not 0x0
>
>>> + u32 sdi_control; /* 0x44 */
>>> + u32 pll_control; /* 0x48 */
>>> +};
>>> +
>>> +/* DISPC Registers */
>>> +struct dispc_regs {
>> similar
>
> ok
>>> + u32 control; /* 0x40 */
>> Tom
>
> Thanks for very detailed review. Mainly Licensing.
Yes.
>
> Regards,
> Khasim
Tom
next prev parent reply other threads:[~2010-01-25 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 13:58 [U-Boot] TI:OMAP: [PATCH 5/7] Add DSS driver for OMAP3 Khasim Syed Mohammed
2010-01-24 0:18 ` Tom
[not found] ` <a8ca84ad1001250558p630a95aeuc6656d4e92cdb6b8@mail.gmail.com>
2010-01-25 14:05 ` [U-Boot] Fwd: " Khasim Syed Mohammed
2010-01-25 14:46 ` Tom [this message]
2010-05-13 14:23 ` John Rigby
2010-05-13 15:37 ` Paulraj, Sandeep
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=4B5DAEBF.2010300@windriver.com \
--to=tom.rix@windriver.com \
--cc=u-boot@lists.denx.de \
/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