All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Tim Harvey <tharvey@gateworks.com>
Cc: u-boot@lists.denx.de, Fabio Estevam <festevam@gmail.com>,
	Peng Fan <peng.fan@nxp.com>, Stefano Babic <sbabic@denx.de>
Subject: Re: [PATCH] ARM: imx: Update Data Modul i.MX8M Mini eDM SBC DRAM timing
Date: Tue, 30 Aug 2022 19:40:53 +0200	[thread overview]
Message-ID: <53fe4f58-fe68-4ddf-a293-f6a6edcad56f@denx.de> (raw)
In-Reply-To: <CAJ+vNU3jekActQ3rtZS+GjiZcqViub+MiV+o5vWj=oyqu4=aOA@mail.gmail.com>

On 8/30/22 18:01, Tim Harvey wrote:

Hi,

> Marek,
> 
> Might I ask how you ran into the issue

There were a couple of boards which were unstable and kept crashing at 
runtime, often when using GPU. Either the machine locked up completely 
or there were rendering artifacts. Eventually also memtester triggered 
on errors during walking ones test.

> and how you came up with the
> new numbers?

The hardware experts ran simulation of the bus in I think hyperlynx and 
come up with new values for the RPA.

> Were the new register settings obtained by simply using a
> newver version of the NXP DDR tool or a new version of the RPA
> Spreadsheet used with the tool or some other means?

Nope, the RPA spreadsheet version was the same, it was the simulation 
the hardware people ran which exposed the sub-optimal inputs into the RPA.

  reply	other threads:[~2022-08-30 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 12:34 [PATCH] ARM: imx: Update Data Modul i.MX8M Mini eDM SBC DRAM timing Marek Vasut
2022-08-30 12:40 ` Fabio Estevam
2022-08-30 16:01 ` Tim Harvey
2022-08-30 17:40   ` Marek Vasut [this message]
2022-09-18 20:41 ` sbabic

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=53fe4f58-fe68-4ddf-a293-f6a6edcad56f@denx.de \
    --to=marex@denx.de \
    --cc=festevam@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=tharvey@gateworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.