public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Grazvydas Ignotas <notasas@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] OMAP3 pandora: Fix CKE1 MUX setting to allow self-refresh
Date: Wed,  8 Jul 2009 00:30:01 +0300	[thread overview]
Message-ID: <1247002201-11345-5-git-send-email-notasas@gmail.com> (raw)
In-Reply-To: <1247002201-11345-4-git-send-email-notasas@gmail.com>

Pandora is using both SDRC CSes. The MUX setting is needed
for the second CS clock signal to allow the 2 RAM parts to
be put in self-refresh correctly.

Based on similar patch for beagle and overo by
Jean Pihet and Steve Sakoman.
---
 board/omap3/pandora/pandora.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/board/omap3/pandora/pandora.h b/board/omap3/pandora/pandora.h
index dfaf32f..f06ee5b 100644
--- a/board/omap3/pandora/pandora.h
+++ b/board/omap3/pandora/pandora.h
@@ -396,6 +396,6 @@ const omap3_sysinfo sysinfo = {
  MUX_VAL(CP(D2D_MBUSFLAG),	(IEN  | PTD | DIS | M0)) /*d2d_mbusflag*/\
  MUX_VAL(CP(D2D_SBUSFLAG),	(IEN  | PTD | DIS | M0)) /*d2d_sbusflag*/\
  MUX_VAL(CP(SDRC_CKE0),		(IDIS | PTU | EN  | M0)) /*sdrc_cke0*/\
- MUX_VAL(CP(SDRC_CKE1),		(IDIS | PTD | DIS | M7)) /*sdrc_cke1*/
+ MUX_VAL(CP(SDRC_CKE1),		(IDIS | PTU | EN  | M0)) /*sdrc_cke1*/
 
 #endif
-- 
1.5.6.3

  reply	other threads:[~2009-07-07 21:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 21:29 [U-Boot] [PATCH 0/4] OMAP3 pandora: pin mux updates Grazvydas Ignotas
2009-07-07 21:29 ` [U-Boot] [PATCH 1/4] OMAP3 pandora: pin mux cleanup Grazvydas Ignotas
2009-07-07 21:29   ` [U-Boot] [PATCH 2/4] OMAP3 pandora: setup pin mux for pins used on rev3 boards Grazvydas Ignotas
2009-07-07 21:30     ` [U-Boot] [PATCH 3/4] OMAP3 pandora: setup pulls for various GPIOs Grazvydas Ignotas
2009-07-07 21:30       ` Grazvydas Ignotas [this message]
2009-07-08 22:44 ` [U-Boot] [PATCH 0/4] OMAP3 pandora: pin mux updates Jean-Christophe PLAGNIOL-VILLARD
2009-07-09 12:20   ` Grazvydas Ignotas

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=1247002201-11345-5-git-send-email-notasas@gmail.com \
    --to=notasas@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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