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: Tue, 13 Jun 2017 05:55:09 +0000 [thread overview]
Message-ID: <1782110.RW4F1b4ZIY@en-pc05> (raw)
In-Reply-To: <AM5PR0402MB285053130F4B1FCBF67C31998CC20@AM5PR0402MB2850.eurprd04.prod.outlook.com>
On Tuesday, June 13, 2017 2:00:16 AM CEST Richard Zhu wrote:
> > -----Original Message-----
> > From: Bjorn Helgaas [mailto:helgaas at kernel.org]
> > Sent: Tuesday, June 13, 2017 7:49 AM
> > To: Stefan Schoefegger <stefan.schoefegger@ginzinger.com>
> > Cc: linux-pci at vger.kernel.org; Richard Zhu <hongxing.zhu@nxp.com>; Arnd
> > Bergmann <arnd@arndb.de>; open list <linux-kernel@vger.kernel.org>;
> > Kishon Vijay Abraham I <kishon@ti.com>; Jingoo Han
> > <jingoohan1@gmail.com>; Bjorn Helgaas <bhelgaas@google.com>;
> > moderated list:PCI DRIVER FOR IMX6 <linux-arm-kernel@lists.infradead.org>;
> > Lucas Stach <l.stach@pengutronix.de>
> > Subject: Re: [PATCH v2 1/1] PCI: imx6: Add pcie compliance test option
> >
> > On Wed, Jun 07, 2017 at 01:36:11PM +0200, Stefan Schoefegger wrote:
> > > Link speed must not be limited to gen1 during link test for compliance
> > > tests
> > >
> > > Signed-off-by: Stefan Schoefegger <stefan.schoefegger@ginzinger.com>
> > > ---
> > >
> > > Changes since v1:
> > > - pci-imx6.c moved to dwc directory
> > >
> > > drivers/pci/dwc/Kconfig | 10 ++++++++++
> > > drivers/pci/dwc/pci-imx6.c | 21 ++++++++++++---------
> > > 2 files changed, 22 insertions(+), 9 deletions(-)
> > >
> > > diff --git a/drivers/pci/dwc/Kconfig b/drivers/pci/dwc/Kconfig index
> > > b7e15526d676..b6e9ced5a45d 100644
> > > --- a/drivers/pci/dwc/Kconfig
> > > +++ b/drivers/pci/dwc/Kconfig
> > > @@ -77,6 +77,16 @@ config PCI_IMX6
> > >
> > > select PCIEPORTBUS
> > > select PCIE_DW_HOST
> > >
> > > +config PCI_IMX6_COMPLIANCE_TEST
> > > + bool "Enable pcie compliance tests on imx6"
> > > + depends on PCI_IMX6
> > > + default n
> > > + help
> > > + Enables support for pcie compliance test on FSL iMX SoCs.
> > > + The link speed wouldn't be limited to gen1 when enabled.
> > > + Enable only during compliance tests, otherwise
> > > + link detection will fail on some peripherals.
> >
> > I'm puzzled about why we would want to merge this patch. It looks like
> > we're trying to game the system to make the device pass compliance testing
> > when it isn't really compliant. Is this config option useful to users, or
> > is it only useful during internal development of iMX SoCs?
>
> [Zhu hongxing] Agree with Bjorn. These modifications shouldn't be merged.
> They are used for the boards used to pass the PCIe RC certification, when
> one Standalone external OSC is used as PCIe reference clock source in the
> boards design.
Yes, passing gen2 compliance test is only possible with external clk. But this
is a errata of imx6 pci phy of PCIe clk jitter. Why should we not be able to
do gen2 tests? I think it is useful to do other gen2 tests (signal integrity)
during board design.
> > > config PCIE_SPEAR13XX
> > >
> > > bool "STMicroelectronics SPEAr PCIe controller"
> > > depends on PCI
> > >
> > > diff --git a/drivers/pci/dwc/pci-imx6.c b/drivers/pci/dwc/pci-imx6.c
> > > index 19a289b8cc94..b0fbe52e25b0 100644
> > > --- a/drivers/pci/dwc/pci-imx6.c
> > > +++ b/drivers/pci/dwc/pci-imx6.c
> > > @@ -533,15 +533,18 @@ static int imx6_pcie_establish_link(struct
> >
> > imx6_pcie *imx6_pcie)
> >
> > > u32 tmp;
> > > int ret;
> > >
> > > - /*
> > > - * Force Gen1 operation when starting the link. In case the link is
> > > - * started in Gen2 mode, there is a possibility the devices on the
> > > - * bus will not be detected at all. This happens with PCIe switches.
> > > - */
> > > - tmp = dw_pcie_readl_dbi(pci, PCIE_RC_LCR);
> > > - tmp &= ~PCIE_RC_LCR_MAX_LINK_SPEEDS_MASK;
> > > - tmp |= PCIE_RC_LCR_MAX_LINK_SPEEDS_GEN1;
> > > - dw_pcie_writel_dbi(pci, PCIE_RC_LCR, tmp);
> > > + if (!IS_ENABLED(CONFIG_PCI_IMX6_COMPLIANCE_TEST)) {
> > > + /*
> > > + * Force Gen1 operation when starting the link. In case the
> > > + * link is started in Gen2 mode, there is a possibility the
> > > + * devices on the bus will not be detected at all. This
> > > + * happens with PCIe switches.
> > > + */
> > > + tmp = dw_pcie_readl_dbi(pci, PCIE_RC_LCR);
> > > + tmp &= ~PCIE_RC_LCR_MAX_LINK_SPEEDS_MASK;
> > > + tmp |= PCIE_RC_LCR_MAX_LINK_SPEEDS_GEN1;
> > > + dw_pcie_writel_dbi(pci, PCIE_RC_LCR, tmp);
> > > + }
> > >
> > > /* Start LTSSM. */
> > > if (imx6_pcie->variant == IMX7D)
> > >
> > > --
> > > 2.11.0
> > >
> > >
> > > _______________________________________________
> > > linux-arm-kernel mailing list
> > > linux-arm-kernel at lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-06-13 5:55 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 [this message]
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
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=1782110.RW4F1b4ZIY@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;
as well as URLs for NNTP newsgroup(s).