From: Archit Taneja <archit@ti.com>
To: "Valkeinen, Tomi" <tomi.valkeinen@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/3] OMAP4: DSS2: Register configuration changes for DSI
Date: Tue, 22 Mar 2011 17:46:44 +0530 [thread overview]
Message-ID: <4D88932C.4050501@ti.com> (raw)
In-Reply-To: <1300795615.2498.99.camel@deskari>
Hi,
On Tuesday 22 March 2011 05:36 PM, Valkeinen, Tomi wrote:
> On Tue, 2011-03-22 at 06:33 -0500, Taneja, Archit wrote:
>> The following changes have changed from OMAP3 to OMAP4 DSI:
>> -The register field DSI_PLL_FREQSEL in DSI_PLL_CONFIGURATION2 has been removed.
>> -DCS_CMD_ENABLE and DCS_CMD_CODE bits have been moved from DSI_CTRL to
>> DSI_VC_CTRLi, hence the control of the bits is available per VC.
>> -DSI LDO powergood notification doesn't work on OMAP4. This is mentioned in
>> OMAP4 errata revision 1.8(Errata 1.76).
>> -OCP_WIDTH register field is included in DSI_VC_CTRL.
>> -The SCP clock is also required to access DSI PLL registers
>>
>> Introduce dss features for these changes so that DSI runs on both OMAP3 and
>> OMAP4.
>>
>> Signed-off-by: Archit Taneja<archit@ti.com>
>> ---
>> drivers/video/omap2/dss/dsi.c | 60 ++++++++++++++++++++-----------
>> drivers/video/omap2/dss/dss_features.c | 9 +++--
>> drivers/video/omap2/dss/dss_features.h | 30 +++++++++-------
>> 3 files changed, 62 insertions(+), 37 deletions(-)
>
> The patch itself looks fine, but the subject says this is part 1/3. But
> I presume this is the only patch.
Yes it is. Sorry for the wrong subject.
Archit
>
> Tomi
>
>
prev parent reply other threads:[~2011-03-22 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 11:33 [PATCH 1/3] OMAP4: DSS2: Register configuration changes for DSI Archit Taneja
2011-03-22 12:06 ` Tomi Valkeinen
2011-03-22 12:16 ` Archit Taneja [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=4D88932C.4050501@ti.com \
--to=archit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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 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.