From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [[PATCH]pandaboard: 1/1] Modification of Elpida DDR2 RAM for Pandaboard-ES Rev B3
Date: Tue, 29 Oct 2013 11:54:55 -0400 [thread overview]
Message-ID: <526FDA4F.6060609@ti.com> (raw)
In-Reply-To: <CAFAe+RtF0nJSGrD9=q8A5-qc+K_fuM85XnXdDftse8_4YUg9Wg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/29/2013 10:17 AM, Hardik Patel wrote:
> Tom, Dan,
>
> Thanks for your feedback on patch.
>
> If I understand correctly, you are suggesting to put static timing
> values for RevB3(instead of putting it for auto detection) in
> "emif_get_reg_dump"
> and "emif_get_dmm_regs_sdp" functions as we do it for other panda
> revisions.
>
> We have already figured out timing values for Elpida RAM on Rev B3.
> However, We need a way to differentiate "Rev-B2" and "Rev-B3", as both
> boards are very similar. We have checked that "omap_revision()" returns
> same value on both B2 and B3.
>
> We have found one difference between both revisions that we may use.
> GPIO171 is '0' for Rev B1/B2, and it comes to '1' for Rev B3. We have
> verified this between two boards.
> * GPIO2, GPIO3, GPIO171, GPIO48, GPIO182: 0 0 0 1 1 => B1/B2
> * GPIO2, GPIO3, GPIO171, GPIO48, GPIO182: 0 0 1 1 1 => B3
>
> Please suggest a correct way to differentiate between B2 and B3 in
> "sdram_elpida.c", so that patch gets accepted.
> Should we export and use "get_board_revision()" along with
> "omap_revision()" in "sdram_elpida.c" to differentiate between B2 and
> B3? In current code "get_board_revision()" is not exported to
> "sdram_elpida.c".
Note that emif_get_device_details is a weak function, so you can just
add one to board/ti/panda/panda.c that will provide the correct data out
of sdram_elpida.c, and not have to modify the function in sdram_elpida.c
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSb9pPAAoJENk4IS6UOR1WJe0QAJZwCubK04YYMVPHcSXPw6ND
TXg1RR/8IC0UWpStKvj4BBobF/M2bemK4Bw+Rfu/tQLLP7Q92/WK0n02VVOYhWTN
kg1FnXDzjGzjvB7KKt+CMftNAYH0PQn1VmbMgQFf4qlteL5oCNT4gZl3YOppYSo5
47g3ckBh51IwwGPPB2hjyFJwWn1IOUtYFEL+HlIXO70fT8Z5hUHcPQPXN/53l3QJ
cM6z7hJV43oSYLjaQ7RBc4FQoU2xfNd2EQpmogd58GC1grVfiDxZ2iDaSNdUBRwk
RcNZRobRkjPDEbG2eLVq+NeFR6UOsEmjB/ZirWOskWnegAqLl3XRBhlUSAg8cJIF
EaBL8M3r/BxH+yn7J2okyTvQ7H2BkUKIqGV1KS5EFCFMAjiFg1Bx3/Ua4NLpDv+N
xIjw0X/XojZ2NIrDXgqOKRKr7Sh5NYqfUSQzyE1t5YJ2k91b8QjNd4vnxsz6iwxe
5d3DXE29nyFgUtcyyJNOm5+nYqOBN9MJOWRFROb8GHFzzgERzW1V07D0W+LSc9cy
Zx7c9SShVWmrKZJHtNDiMetUV6pqDU3v1BTXkqw0ocF/uwm0Il0uvk/GrNs1+D62
WziWXd5qXok67Ynmrf1gsE8Ol29Axf1Br1H2DPgqfkUr2pI57vX2x8UbQen+4Zie
lO5ipCHEw6czTUMz/5o+
=Mfm1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-10-29 15:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 15:42 [U-Boot] [[PATCH]pandaboard: 0/1] Modification of Elpida DDR2 RAM for Pandaboard-ES Rev B3 Hardik
2013-10-25 15:42 ` [U-Boot] [[PATCH]pandaboard: 1/1] " Hardik
2013-10-28 12:51 ` Dan Murphy
2013-10-28 13:04 ` Tom Rini
2013-10-29 14:17 ` Hardik Patel
2013-10-29 15:54 ` Tom Rini [this message]
2013-11-14 10:05 ` [U-Boot] [[PATCH v2]pandaboard: 0/1] " Hardik
2013-11-14 10:06 ` Hardik
2013-11-14 10:06 ` [U-Boot] [[PATCH v2]pandaboard: 1/1] " Hardik
2013-11-14 15:29 ` Robert Nelson
2013-11-14 15:41 ` Michael Trimarchi
2013-11-14 16:19 ` Tom Rini
2013-11-14 16:28 ` Michael Trimarchi
2013-11-14 16:32 ` Tom Rini
2013-11-14 18:43 ` Hardik Patel
2013-11-14 18:58 ` Michael Trimarchi
2013-11-14 19:02 ` Tom Rini
2013-11-14 19:41 ` Nishanth Menon
2013-11-14 19:49 ` Tom Rini
2013-11-14 20:26 ` Nishanth Menon
2013-11-21 9:17 ` jmgrimaud
2013-11-27 15:46 ` [U-Boot] [[PATCH v3]pandaboard: 0/1] ARM:OMAP4+: panda-es: Support Rev B3 Elpida DDR2 RAM Hardik
2013-11-27 15:46 ` [U-Boot] [[PATCH v3]pandaboard: 1/1] " Hardik
2013-12-04 22:05 ` [U-Boot] [U-Boot, [PATCH, v3] pandaboard: " Tom Rini
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=526FDA4F.6060609@ti.com \
--to=trini@ti.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