U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Eichenberger <stefan.eichenberger@netmodule.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Armada 385: PEX detection pulse width
Date: Fri, 21 Apr 2017 10:51:06 +0200	[thread overview]
Message-ID: <20170421085105.GA6180@gruene.netmodule.intranet> (raw)

Dear Adam,

On the mainline u-boot we found a commit which helps to fix a problem
regarding PCIe and the Armada 370:
http://git.denx.de/?p=u-boot.git;a=commit;h=6bbe0924a799d33c1a8c9de38b60a5e0251f2aea

We currently facing a similar problem with the Armada 385 and PCIe. The
problem also appears with two different Atheros chipsets one (AR9280) 
gets never detected and the other one gets detected most of the time but 
not always (QCA9882). With Intel modules on the other hand, we can't 
reproduce the issue. It's the same behaviour as described in the commit
above, the link training fails and therefore the link is signalized as 
down. If a link is successfully established (QCA9882) we don't see any 
errors during communication.

Do you know if we have the same possibility on the Armada 385 to tune
the PCI Express pulse width as you proposed it for the Armada 370?
Unfortunately the PCIe Phy seems to be quite different to the one from
the Armada 370.

Best regards
Stefan

             reply	other threads:[~2017-04-21  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  8:51 Stefan Eichenberger [this message]
2017-04-23 17:28 ` [U-Boot] [EXT] Armada 385: PEX detection pulse width Adam Shobash
2017-04-25  5:43   ` Rene Straub
2017-04-25  7:25     ` Adam Shobash
2017-04-25  7:52       ` Assaf Hoffman

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=20170421085105.GA6180@gruene.netmodule.intranet \
    --to=stefan.eichenberger@netmodule.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