All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: u-boot@lists.denx.de
Subject: [PATCH u-boot-marvell] PLEASE TEST ddr: marvell: a38x: fix SPLIT_OUT_MIX state decision
Date: Mon, 8 Feb 2021 20:14:26 +0000	[thread overview]
Message-ID: <f9cf72e9-10f3-57d0-917f-5be0ac21bebd@alliedtelesis.co.nz> (raw)
In-Reply-To: <20210208201534.717a610a@nic.cz>

On 9/02/21 8:15 am, Marek Behun wrote:
> This patch is needed on some Turris Omnia boards with Samsung DDR chips,
> otherwise DDR training fails in ~60% of cases.
>
> Marvell send us this patch for testing, I have updated it a little.
>
> Please test this on other A38x boards.
>
> If it doesn't break anything on other boards, we can apply it and send
> it to mv-ddr-marvell upstream.
They gave us the same patch. I was hoping their SoC team would get it 
into mv-ddr-marvell (or even their vendor USP) but obviously they're 
still sitting on it. I know it improved matters for some of our boards 
but it didn't totally fix them we still had yield problems when we 
ramped up production.

  reply	other threads:[~2021-02-08 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 19:12 [PATCH u-boot-marvell] PLEASE TEST ddr: marvell: a38x: fix SPLIT_OUT_MIX state decision Marek Behún
2021-02-08 19:15 ` Marek Behun
2021-02-08 20:14   ` Chris Packham [this message]
2021-02-08 20:24     ` Marek Behun
2021-06-28  7:20       ` Pali Rohár
2021-06-28  9:21         ` Chris Packham
2021-06-28  9:53           ` Chris Packham
2022-01-04 20:28 Marek Behún
2022-01-04 22:10 ` Chris Packham
2022-01-05  9:10   ` Marek Behún
2022-01-05 22:51     ` Chris Packham
2022-01-06  3:04       ` Chris Packham

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=f9cf72e9-10f3-57d0-917f-5be0ac21bebd@alliedtelesis.co.nz \
    --to=chris.packham@alliedtelesis.co.nz \
    --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.