From: Eric Nelson <eric@nelint.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] arm: imx6: Add DDR3 calibration code for MX6 Q/D/DL
Date: Tue, 22 Dec 2015 07:47:47 -0700 [thread overview]
Message-ID: <56796293.9040603@nelint.com> (raw)
In-Reply-To: <CAJ+vNU1pAfwQuWfn1zKYkFgi2yV0P-35XCYo5uKTOLd7h5cmqg@mail.gmail.com>
Hi Tim,
On 12/21/2015 09:13 PM, Tim Harvey wrote:
> On Sun, Dec 20, 2015 at 11:31 AM, Eric Nelson <eric@nelint.com> wrote:
>> Hi Marek,
>>
> <snip>
>> I'd recommend passing parameters of mx6_ddr_sysinfo (input) and
>> mx6_mmdc_calibration (output) to this routine.
>>
>
> I don't know that this would make sense. The mx6_ddr_sysinfo shouldn't
> be affected by calibration and the mx6_mmdc_calibration structure
> would not be used if you are using auto-calibration.
>
> In fact, I recommend an additional patch that will call the
> auto-calibration functions in mx6_ddr3_cfg if it is passed a NULL for
> mx6_ddr_calibration.
>
Using sysinfo allows simpler determination of things like bus size
and rtt_nom.
This should be based on a board's configuration instead of inferring
the parameters by reading and interpreting registers that must
have been set before the calls to do_write_level_calibration().
The DDR stress tool does this (read from registers) because it's
distributed as a binary and JTAG is used to configure things before
running.
The calibration parameter would be used in a subsequent patch to
add a "calibration" pseudo-board.
Regards,
Eric
prev parent reply other threads:[~2015-12-22 14:47 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 14:40 [U-Boot] [PATCH 1/2] arm: imx6: Add DDR3 calibration code for MX6 Q/D/DL Marek Vasut
2015-12-16 14:40 ` [U-Boot] [PATCH 2/2] arm: imx6: Enable DDR calibration on Novena Marek Vasut
2015-12-20 19:46 ` Eric Nelson
[not found] ` <567702A6.9070107@cox.net>
2015-12-22 1:26 ` Marek Vasut
2015-12-22 8:30 ` Nikolay Dimitrov
2015-12-22 14:56 ` Marek Vasut
2015-12-16 15:00 ` [U-Boot] [PATCH 1/2] arm: imx6: Add DDR3 calibration code for MX6 Q/D/DL Eric Nelson
2015-12-16 15:33 ` Marek Vasut
2015-12-16 16:28 ` Eric Nelson
2015-12-16 16:50 ` Marek Vasut
2015-12-16 17:07 ` Eric Nelson
2015-12-16 17:11 ` Marek Vasut
2015-12-17 15:39 ` Tim Harvey
2015-12-17 15:48 ` Eric Nelson
2015-12-17 15:36 ` Tim Harvey
2015-12-17 15:40 ` Marek Vasut
2015-12-17 16:15 ` Tim Harvey
2015-12-17 16:17 ` Marek Vasut
2015-12-17 21:32 ` Nikolay Dimitrov
2015-12-17 22:11 ` Marek Vasut
2015-12-20 19:31 ` Eric Nelson
2015-12-22 1:52 ` Marek Vasut
2015-12-22 15:37 ` Eric Nelson
2016-01-14 2:10 ` Marek Vasut
2016-01-14 2:37 ` Eric Nelson
2016-01-14 2:50 ` Marek Vasut
2016-01-14 2:52 ` Eric Nelson
2016-01-14 3:06 ` Marek Vasut
2016-01-14 14:25 ` Tim Harvey
2016-01-24 10:47 ` Stefano Babic
2016-01-24 16:01 ` Marek Vasut
2016-01-24 17:03 ` Stefano Babic
2016-01-24 17:11 ` Marek Vasut
2016-01-24 17:18 ` Stefano Babic
2016-01-24 17:22 ` Marek Vasut
2016-01-24 19:33 ` Tom Rini
2016-01-24 22:07 ` Marek Vasut
2016-01-24 22:21 ` Tom Rini
2016-01-24 23:00 ` Marek Vasut
2016-01-24 23:30 ` Tom Rini
2016-01-24 23:55 ` Marek Vasut
2016-01-31 17:25 ` Marek Vasut
2016-06-02 13:20 ` Tim Harvey
2016-06-02 14:23 ` Stefano Babic
2016-06-02 15:25 ` Tim Harvey
2015-12-22 4:13 ` Tim Harvey
2015-12-22 14:47 ` Eric Nelson [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=56796293.9040603@nelint.com \
--to=eric@nelint.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