public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Archit Taneja <a0393947@ti.com>
Cc: 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: Thu, 19 Apr 2012 14:05:52 +0300	[thread overview]
Message-ID: <1334833552.1911.20.camel@deskari> (raw)
In-Reply-To: <20120419093158.GX25053@n2100.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]

On Thu, 2012-04-19 at 10:31 +0100, Russell King - ARM Linux wrote:
> On Wed, Apr 18, 2012 at 01:43:46PM +0530, Archit Taneja wrote:
> > 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.
> 
> I was just going to ask about this, as I haven't noticed any improvement
> in mainline kernels since I reported the original failure...

It seems to be very difficult to find out why the TRM change was done,
and what the HW actually does. But as the boards out there are clearly
fixed by reverting the original patch, I think it's best if we just
apply the revert.

Archit, can you resend the patch with my ack, and cc
stable@vger.kernel.org (see Documentation/stable_kernel_rules.txt).

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-04-19 11:05 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
2012-04-19  9:31     ` Russell King - ARM Linux
2012-04-19 11:05       ` Tomi Valkeinen [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=1334833552.1911.20.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox