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] arm: mvebu: update RTC values for PCIe memory wrappers
Date: Wed, 26 Feb 2020 06:52:01 +0000	[thread overview]
Message-ID: <04b26a4c6b68a902266bd2160cbc3371eede2e9f.camel@alliedtelesis.co.nz> (raw)
In-Reply-To: <41312d93e1bdf4db55d81e9cd1c17a7073ea8a81.camel@alliedtelesis.co.nz>

On Wed, 2020-02-26 at 19:46 +1300, Chris Packham wrote:
> Hi Baruch,
> 
> On Wed, 2020-02-26 at 06:49 +0200, Baruch Siach wrote:
> > Hi Chris,
> > 
> > On Wed, Feb 26 2020, Chris Packham wrote:
> > > From: Chris Packham <chris.packham@alliedtelesis.co.nz>
> > > 
> > > Update the RTC (Read Timing Control) values for PCIe memory
> > > wrappers
> > > following an ERRATA (ERRATA# TDB). This means the PCIe accesses
> > > will
> > > used slower memory Read Timing, to allow more efficient energy
> > > consumption, in order to lower the minimum VDD of the
> > > memory.  Will
> > > lead
> > > to more robust memory when voltage drop occurs (VDDSEG)
> > 
> > Have you seen memory access reliability problems because of this
> > issue?
> > 
> 
> We're seeing a few different symptoms but they all consist of a PCIe
> transfer failing in some way (as far as we can tell in the TX
> direction
> from the CPU).
> 
> > > The code is based on changes from Marvell's U-Boot, specifically:
> > > 
> > > 
> 
> 
https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/commit/20cd2704072512de176e048970f2883db901674b
> > > 
> 
> 
https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/commit/eb608a7c8dd0d42b87601a61b9c0cc5615ab94b2
> > > 
> 
> 
https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/commit/c4af19ae2bf08cf6e450e741ce4f04d402a5cb6b
> > > 
> 
> 
https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/commit/c4af19ae2bf08cf6e450e741ce4f04d402a5cb6b
> > 
> > The last link looks duplicated.
> 
> Hmm I was pretty sure there were 4 commits. I'll double check and
> either fix or remove the link.

Ah. There are 4 patches, but the last one isn't in the github repo for
some reason. I'll drop the link.

> 
> > 
> > baruch
> > 

      reply	other threads:[~2020-02-26  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26  0:02 [PATCH] arm: mvebu: update RTC values for PCIe memory wrappers Chris Packham
2020-02-26  4:49 ` Baruch Siach
2020-02-26  6:46   ` Chris Packham
2020-02-26  6:52     ` Chris Packham [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=04b26a4c6b68a902266bd2160cbc3371eede2e9f.camel@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.