From: Stefan.Schoefegger@ginzinger.com (Schöfegger Stefan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/1] PCI: imx6: Add pcie compliance test option
Date: Mon, 19 Jun 2017 06:43:58 +0000 [thread overview]
Message-ID: <1552752.riIkOpKaxW@en-pc05> (raw)
In-Reply-To: <CAOMZO5C03MwGkQSrJr-AeG98q84iyWnKj2GSvveJ6xKL+Y-9EQ@mail.gmail.com>
On Wednesday, June 14, 2017 4:11:29 PM CEST Fabio Estevam wrote:
> On Wed, Jun 14, 2017 at 2:52 AM, Sch?fegger Stefan
>
> <Stefan.Schoefegger@ginzinger.com> wrote:
> > device). The bitrate and de-emphasis must be switched. The driver (without
> > this patches) does not allow to switch to gen2 because it falls back to
> > gen1. It is impossible to generate the gen2 test pattern.
>
> If you pass 'fsl,max-link-speed = <2>;' in your device tree, then it
> will allow gen2.
>
> From Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt:
>
> "- fsl,max-link-speed: Specify PCI gen for link capability. Must be '2' for
> gen2, otherwise will default to gen1. Note that the IMX6 LVDS clock
> outputs do not meet gen2 jitter requirements and thus for gen2 capability a
> gen2 compliant clock generator should be used and configured."
>
> Wouldn't this solve the problem?
No, it only sets the maximum allowed link speed but it is forced to gen1
before.
During compliance test there is no real link established and there is no link
speed negotiation, the phy is in a special compliance test state.
Stefan
prev parent reply other threads:[~2017-06-19 6:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 10:38 [PATCH 1/1] PCI: imx6: Add pcie compliance test option Stefan Schoefegger
2017-06-07 11:36 ` [PATCH v2 " Stefan Schoefegger
2017-06-12 23:49 ` Bjorn Helgaas
2017-06-13 2:00 ` Richard Zhu
2017-06-13 5:55 ` Schöfegger Stefan
2017-06-13 5:43 ` Schöfegger Stefan
2017-06-13 13:58 ` Bjorn Helgaas
2017-06-14 5:52 ` Schöfegger Stefan
2017-06-14 19:11 ` Fabio Estevam
2017-06-19 6:43 ` Schöfegger Stefan [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=1552752.riIkOpKaxW@en-pc05 \
--to=stefan.schoefegger@ginzinger.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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