All of lore.kernel.org
 help / color / mirror / Atom feed
From: Archit Taneja <a0393947@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux@arm.linux.org.uk, tony@atomide.com,
	linux-omap@vger.kernel.org, santosh.shilimkar@ti.com,
	paul@pwsan.com, b-cousson@ti.com
Subject: Re: [PATCH] ARM: OMAP: Revert "ARM: OMAP: ctrl: Fix CONTROL_DSIPHY register fields"
Date: Wed, 18 Apr 2012 13:43:46 +0530	[thread overview]
Message-ID: <4F8E77BA.3000507@ti.com> (raw)
In-Reply-To: <1334736386.1886.8.camel@deskari>

On Wednesday 18 April 2012 01:36 PM, Tomi Valkeinen wrote:
> Hi,
>
> On Mon, 2012-04-09 at 12:41 +0530, Archit Taneja wrote:
>> This reverts commit 46f8c3c7e95c0d30d95911e7975ddc4f93b3e237.
>>
>> The commit above swapped the DSI1_PPID and DSI2_PPID register fields in
>> CONTROL_DSIPHY to be in sync with the newer public OMAP TRMs(after version V).
>>
>> With this commit, contention errors were reported on DSI lanes some OMAP4 SDPs.
>> After probing the DSI lanes on OMAP4 SDP, it was seen that setting bits in the
>> DSI2_PPID field was pulling up voltage on DSI1 lanes, and DSI1_PPID field was
>> pulling up voltage on DSI2 lanes.
>>
>> This proves that the current version of OMAP4 TRM is incorrect, swap the
>> position of register fields according to the older TRM versions as they were
>> correct.
>
> Are we sure the bits are the same for all OMAP4 versions? I'm just
> wondering why the change was made to TRM...

I've tried on OMAP4430 ES2.1 and OMAP4460 ES1.1. I can try on a couple 
more revisions.

As far as why the change was made in the TRM, it's a bit hard to find 
the right people, or get response from them :), I'll give that a try again.

If we do conclude that this revert patch is needed, it might probably be 
a candidate for the 3.2 and 3.3 stable kernels, just wanted to point 
that out.

Archit

>
>   Tomi
>


  reply	other threads:[~2012-04-18  8:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09  7:11 [PATCH] ARM: OMAP: Revert "ARM: OMAP: ctrl: Fix CONTROL_DSIPHY register fields" Archit Taneja
2012-04-09 23:02 ` Tony Lindgren
2012-04-18  8:06 ` Tomi Valkeinen
2012-04-18  8:13   ` Archit Taneja [this message]
2012-04-19  9:31     ` Russell King - ARM Linux
2012-04-19 11:05       ` Tomi Valkeinen

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=4F8E77BA.3000507@ti.com \
    --to=a0393947@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=tony@atomide.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.