From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] mx6slevk: imximage.cfg: update to fix tINIT3 and tIH-CA violations
Date: Tue, 5 Apr 2016 09:43:11 -0400 [thread overview]
Message-ID: <20160405134311.GD23166@bill-the-cat> (raw)
In-Reply-To: <20160405085326.GA30800@linux-7smt.suse>
On Tue, Apr 05, 2016 at 04:53:28PM +0800, Peng Fan wrote:
> Hi Tom,
>
> I know this already merged to i.mx tree. I still have a question for the
> tIH-CA violation.
It's not in mainline 'tho so it can always come out :)
> In my side, the value is ok. clk is 400MHz.
> (0x30 * 256.0) * (1000000000000.0/400000000.0) = 468.75ps.
> And according to spec, to 800M date rate, the minimum tIH value is 290ps.
>
> So I wonder how in your side it is tIH-CA violation.
The board we measured this on is based on the mx6slevk and this
particular part of the board (layout, etc) is unchanged. Micron put the
board under analysis and measured these violations (along with that we
don't issue a reset before configuring CS1, I still might try and push
that change up for the EVK at least, not armadillo tho).
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160405/2d04f439/attachment.sig>
next prev parent reply other threads:[~2016-04-05 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 21:54 [U-Boot] [PATCH 0/2] i.MX6 LPDDR2 fixes Tom Rini
2016-04-01 21:54 ` [U-Boot] [PATCH 1/2] mx6qarm2: imximage_mx6dl.cfg update to fix tINIT3 violation Tom Rini
2016-04-03 17:22 ` Stefano Babic
2016-04-01 21:54 ` [U-Boot] [PATCH 2/2] mx6slevk: imximage.cfg: update to fix tINIT3 and tIH-CA violations Tom Rini
2016-04-01 23:58 ` Fabio Estevam
2016-04-03 17:22 ` Stefano Babic
2016-04-03 18:06 ` Tom Rini
2016-04-05 8:53 ` Peng Fan
2016-04-05 13:43 ` Tom Rini [this message]
2016-04-05 14:01 ` Stefano Babic
2016-04-06 4:45 ` Peng Fan
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=20160405134311.GD23166@bill-the-cat \
--to=trini@konsulko.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