public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Raghuveer Murthy <x0075817@ti.com>
To: "Valkeinen, Tomi" <tomi.valkeinen@ti.com>
Cc: "Murthy, Raghuveer" <raghuveer.murthy@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [3/4] OMAP: DSS2: Adding macro for DISPC_DIVISOR register
Date: Thu, 17 Feb 2011 12:47:54 +0530	[thread overview]
Message-ID: <4D5CCBA2.80204@ti.com> (raw)
In-Reply-To: <1297870985.14556.14.camel@deskari>

On Wednesday 16 February 2011 09:13 PM, Valkeinen, Tomi wrote:
> On Thu, 2011-02-03 at 14:09 +0000, Raghuveer Murthy wrote:
>> Added macro for DISPC_DIVISOR. This is different from DISPC_DIVISOR1 and
>> DISPC_DIVISOR2. OMAP4 supports all the above 3 registers.
>>
>> DISPC_DIVISOR1 and DISPC_DIVISOR2 registers are accessed through
>> DISPC_DIVISORo(ch) macro
>>
>> Signed-off-by: Raghuveer Murthy<raghuveer.murthy@ti.com>
>>
>> ---
>> drivers/video/omap2/dss/dispc.c |   11 +++++++++++
>>   1 files changed, 11 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/video/omap2/dss/dispc.c b/drivers/video/omap2/dss/dispc.c
>> index e52a413..6225d12 100644
>> --- a/drivers/video/omap2/dss/dispc.c
>> +++ b/drivers/video/omap2/dss/dispc.c
>> @@ -132,6 +132,17 @@ struct dispc_reg { u16 idx; };
>>
>>   #define DISPC_VID_PRELOAD(n)		DISPC_REG(0x230 + (n)*0x04)
>>
>> +/*
>> + * The OMAP4 DISPC_DIVISOR1 is backward compatible to OMAP3xxx DISPC_DIVISOR.
>> + * However DISPC_DIVISOR is also provided in OMAP4, to control DISPC_CORE_CLK.
>> + * This allows DISPC_CORE_CLK to be independent of logical clock dividers (lcd)
>> + * of LCD1 (primary) and LCD2 (secondary) displays.
>> + *
>> + * To derive pixel clocks for Primary and Secondary LCD channels, configure the
>> + * lcd and pcd in DISPC_DIVISOR1 and DISPC_DIVISOR2 respectively, using the
>> + * DISPC_DIVISORo(ch).
>> + */
>> +#define DISPC_DIVISOR			DISPC_REG(0x0804)
>>
>>   #define DISPC_IRQ_MASK_ERROR            (DISPC_IRQ_GFX_FIFO_UNDERFLOW | \
>>   					 DISPC_IRQ_OCP_ERR | \
>
> See my comment about comments in previous mail.
>
> I think you should merge this and the next patch. There's not much point
> in adding a single line define, which is not used (yet).
>
> How about the debug output from debug/omapdss/clk file? Does it print
> sensible things on OMAP4 after these patches?

Will verify this.
>
>   Tomi
>
>

Acknowledge the comments for patch 2/4 and 3/4. Will merge them and post 
a new series.

Regards,
Raghuveer

  reply	other threads:[~2011-02-17  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 14:09 [PATCH 0/4] OMAP: DSS2: Fix for DISPC core functional clock divider Raghuveer Murthy
2011-02-03 14:09 ` [PATCH 1/4] OMAP: DSS2: Adding dss_features for independent core clk divider Raghuveer Murthy
2011-02-03 14:09 ` [PATCH 2/4] OMAP: DSS2: Renaming register macro DISPC_DIVISOR(ch) Raghuveer Murthy
2011-02-16 15:38   ` [2/4] " Tomi Valkeinen
2011-02-03 14:09 ` [PATCH 3/4] OMAP: DSS2: Adding macro for DISPC_DIVISOR register Raghuveer Murthy
2011-02-16 15:43   ` [3/4] " Tomi Valkeinen
2011-02-17  7:17     ` Raghuveer Murthy [this message]
2011-02-03 14:09 ` [PATCH 4/4] OMAP4: DSS2: Using dss_features to set independent core clock divider Raghuveer Murthy

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=4D5CCBA2.80204@ti.com \
    --to=x0075817@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=raghuveer.murthy@ti.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox