linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Archit Taneja <archit@ti.com>
Cc: tomi.valkeinen@ti.com, linux@arm.linux.org.uk,
	linux-omap@vger.kernel.org, santosh.shilimkar@ti.com,
	paul@pwsan.com, b-cousson@ti.com, stable@vger.kernel.org
Subject: Re: [PATCH RESEND] ARM: OMAP: Revert "ARM: OMAP: ctrl: Fix CONTROL_DSIPHY register fields"
Date: Fri, 4 May 2012 12:14:56 -0700	[thread overview]
Message-ID: <20120504191456.GO5613@atomide.com> (raw)
In-Reply-To: <1334837356-2440-1-git-send-email-archit@ti.com>

* Archit Taneja <archit@ti.com> [120419 05:13]:
> 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.

Thanks applying into fixes.

Tony
 
> Cc: stable@vger.kernel.org # v3.2+
> Acked-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Signed-off-by: Archit Taneja <archit@ti.com>
> ---
> Note: Resend with stable kernel list added in cc
> 
>  .../include/mach/ctrl_module_pad_core_44xx.h       |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/include/mach/ctrl_module_pad_core_44xx.h b/arch/arm/mach-omap2/include/mach/ctrl_module_pad_core_44xx.h
> index 1e2d332..c88420d 100644
> --- a/arch/arm/mach-omap2/include/mach/ctrl_module_pad_core_44xx.h
> +++ b/arch/arm/mach-omap2/include/mach/ctrl_module_pad_core_44xx.h
> @@ -941,10 +941,10 @@
>  #define OMAP4_DSI2_LANEENABLE_MASK				(0x7 << 29)
>  #define OMAP4_DSI1_LANEENABLE_SHIFT				24
>  #define OMAP4_DSI1_LANEENABLE_MASK				(0x1f << 24)
> -#define OMAP4_DSI2_PIPD_SHIFT					19
> -#define OMAP4_DSI2_PIPD_MASK					(0x1f << 19)
> -#define OMAP4_DSI1_PIPD_SHIFT					14
> -#define OMAP4_DSI1_PIPD_MASK					(0x1f << 14)
> +#define OMAP4_DSI1_PIPD_SHIFT					19
> +#define OMAP4_DSI1_PIPD_MASK					(0x1f << 19)
> +#define OMAP4_DSI2_PIPD_SHIFT					14
> +#define OMAP4_DSI2_PIPD_MASK					(0x1f << 14)
>  
>  /* CONTROL_MCBSPLP */
>  #define OMAP4_ALBCTRLRX_FSX_SHIFT				31
> -- 
> 1.7.5.4
> 

  reply	other threads:[~2012-05-04 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 12:09 [PATCH RESEND] ARM: OMAP: Revert "ARM: OMAP: ctrl: Fix CONTROL_DSIPHY register fields" Archit Taneja
2012-05-04 19:14 ` Tony Lindgren [this message]
2012-05-07 11:01 ` Archit Taneja
2012-05-08 23:20   ` Tony Lindgren

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=20120504191456.GO5613@atomide.com \
    --to=tony@atomide.com \
    --cc=archit@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=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).