From: Rob Herring <robh@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: PCI <linux-pci@vger.kernel.org>,
"Jason Cooper" <jason@lakedaemon.net>,
"Andrew Lunn" <andrew@lunn.ch>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Andrew Murray" <amurray@thegoodpenguin.co.uk>,
"Remi Pommarel" <repk@triplefau.lt>,
"Tomasz Maciej Nowak" <tmn505@gmail.com>,
Xogium <contact@xogium.me>, "Marek Behún" <marek.behun@nic.cz>,
"Bjorn Helgaas" <helgaas@kernel.org>
Subject: Re: [PATCH v3 04/12] PCI: aardvark: Improve link training
Date: Fri, 24 Apr 2020 12:00:54 -0500 [thread overview]
Message-ID: <CAL_JsqLTXGE4SAmbzkPJ-omusMiSoBwgF0j8HhAq7F+9w7g1wg@mail.gmail.com> (raw)
In-Reply-To: <20200424153858.29744-5-pali@kernel.org>
On Fri, Apr 24, 2020 at 10:39 AM Pali Rohár <pali@kernel.org> wrote:
>
> From: Marek Behún <marek.behun@nic.cz>
>
> Currently the aardvark driver trains link in PCIe gen2 mode. This may
> cause some buggy gen1 cards (such as Compex WLE900VX) to be unstable or
> even not detected. Moreover when ASPM code tries to retrain link second
> time, these cards may stop responding and link goes down. If gen1 is
> used this does not happen.
>
> Unconditionally forcing gen1 is not a good solution since it may have
> performance impact on gen2 cards.
>
> To overcome this, read 'max-link-speed' property (as defined in PCI
> device tree bindings) and use this as max gen mode. Then iteratively try
> link training at this mode or lower until successful. After successful
> link training choose final controller gen based on Negotiated Link Speed
> from Link Status register, which should match card speed.
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
> Signed-off-by: Marek Behún <marek.behun@nic.cz>
> ---
> drivers/pci/controller/pci-aardvark.c | 113 ++++++++++++++++++++------
> 1 file changed, 88 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/pci/controller/pci-aardvark.c b/drivers/pci/controller/pci-aardvark.c
> index 74b90940a9d4..a6c4d4d52631 100644
> --- a/drivers/pci/controller/pci-aardvark.c
> +++ b/drivers/pci/controller/pci-aardvark.c
> @@ -40,6 +40,7 @@
> #define PCIE_CORE_LINK_CTRL_STAT_REG 0xd0
> #define PCIE_CORE_LINK_L0S_ENTRY BIT(0)
> #define PCIE_CORE_LINK_TRAINING BIT(5)
> +#define PCIE_CORE_LINK_SPEED_SHIFT 16
> #define PCIE_CORE_LINK_WIDTH_SHIFT 20
> #define PCIE_CORE_ERR_CAPCTL_REG 0x118
> #define PCIE_CORE_ERR_CAPCTL_ECRC_CHK_TX BIT(5)
> @@ -201,6 +202,7 @@ struct advk_pcie {
> struct mutex msi_used_lock;
> u16 msi_msg;
> int root_bus_nr;
> + int link_gen;
> struct pci_bridge_emul bridge;
> };
>
> @@ -225,20 +227,16 @@ static int advk_pcie_link_up(struct advk_pcie *pcie)
>
> static int advk_pcie_wait_for_link(struct advk_pcie *pcie)
> {
> - struct device *dev = &pcie->pdev->dev;
> int retries;
>
> /* check if the link is up or not */
> for (retries = 0; retries < LINK_WAIT_MAX_RETRIES; retries++) {
> - if (advk_pcie_link_up(pcie)) {
> - dev_info(dev, "link up\n");
> + if (advk_pcie_link_up(pcie))
> return 0;
> - }
>
> usleep_range(LINK_WAIT_USLEEP_MIN, LINK_WAIT_USLEEP_MAX);
> }
>
> - dev_err(dev, "link never came up\n");
> return -ETIMEDOUT;
> }
>
> @@ -253,6 +251,85 @@ static void advk_pcie_wait_for_retrain(struct advk_pcie *pcie)
> }
> }
>
> +static int advk_pcie_train_at_gen(struct advk_pcie *pcie, int gen)
> +{
> + int ret, neg_gen;
> + u32 reg;
> +
> + /* Setup link speed */
> + reg = advk_readl(pcie, PCIE_CORE_CTRL0_REG);
> + reg &= ~PCIE_GEN_SEL_MSK;
> + if (gen == 3)
> + reg |= SPEED_GEN_3;
> + else if (gen == 2)
> + reg |= SPEED_GEN_2;
> + else
> + reg |= SPEED_GEN_1;
> + advk_writel(pcie, reg, PCIE_CORE_CTRL0_REG);
> +
> + /*
> + * Enable link training. This is not needed in every call to this
> + * function, just once suffices, but it does not break anything either.
> + */
> + reg = advk_readl(pcie, PCIE_CORE_CTRL0_REG);
> + reg |= LINK_TRAINING_EN;
> + advk_writel(pcie, reg, PCIE_CORE_CTRL0_REG);
> +
> + /*
> + * Start link training immediately after enabling it.
> + * This solves problems for some buggy cards.
> + */
> + reg = advk_readl(pcie, PCIE_CORE_LINK_CTRL_STAT_REG);
> + reg |= PCIE_CORE_LINK_TRAINING;
> + advk_writel(pcie, reg, PCIE_CORE_LINK_CTRL_STAT_REG);
> +
> + ret = advk_pcie_wait_for_link(pcie);
> + if (ret)
> + return ret;
> +
> + reg = advk_readl(pcie, PCIE_CORE_LINK_CTRL_STAT_REG);
> + neg_gen = (reg >> PCIE_CORE_LINK_SPEED_SHIFT) & 0xf;
> +
> + return neg_gen;
> +}
> +
> +static void advk_pcie_train_link(struct advk_pcie *pcie)
> +{
> + struct device *dev = &pcie->pdev->dev;
> + int neg_gen = -1, gen;
> +
> + /*
> + * Try link training at link gen specified by device tree property
> + * 'max-link-speed'. If this fails, iteratively train at lower gen.
> + */
> + for (gen = pcie->link_gen; gen > 0; --gen) {
> + neg_gen = advk_pcie_train_at_gen(pcie, gen);
> + if (neg_gen > 0)
> + break;
> + }
> +
> + if (neg_gen < 0)
> + goto err;
> +
> + /*
> + * After successful training if negotiated gen is lower than requested,
> + * train again on negotiated gen. This solves some stability issues for
> + * some buggy gen1 cards.
> + */
> + if (neg_gen < gen) {
> + gen = neg_gen;
> + neg_gen = advk_pcie_train_at_gen(pcie, gen);
> + }
> +
> + if (neg_gen == gen) {
> + dev_info(dev, "link up at gen %i\n", gen);
> + return;
> + }
> +
> +err:
> + dev_err(dev, "link never came up\n");
> +}
> +
> static void advk_pcie_setup_hw(struct advk_pcie *pcie)
> {
> u32 reg;
> @@ -288,12 +365,6 @@ static void advk_pcie_setup_hw(struct advk_pcie *pcie)
> PCIE_CORE_CTRL2_TD_ENABLE;
> advk_writel(pcie, reg, PCIE_CORE_CTRL2_REG);
>
> - /* Set GEN2 */
> - reg = advk_readl(pcie, PCIE_CORE_CTRL0_REG);
> - reg &= ~PCIE_GEN_SEL_MSK;
> - reg |= SPEED_GEN_2;
> - advk_writel(pcie, reg, PCIE_CORE_CTRL0_REG);
> -
> /* Set lane X1 */
> reg = advk_readl(pcie, PCIE_CORE_CTRL0_REG);
> reg &= ~LANE_CNT_MSK;
> @@ -341,20 +412,7 @@ static void advk_pcie_setup_hw(struct advk_pcie *pcie)
> */
> msleep(PCI_PM_D3COLD_WAIT);
>
> - /* Enable link training */
> - reg = advk_readl(pcie, PCIE_CORE_CTRL0_REG);
> - reg |= LINK_TRAINING_EN;
> - advk_writel(pcie, reg, PCIE_CORE_CTRL0_REG);
> -
> - /*
> - * Start link training immediately after enabling it.
> - * This solves problems for some buggy cards.
> - */
> - reg = advk_readl(pcie, PCIE_CORE_LINK_CTRL_STAT_REG);
> - reg |= PCIE_CORE_LINK_TRAINING;
> - advk_writel(pcie, reg, PCIE_CORE_LINK_CTRL_STAT_REG);
> -
> - advk_pcie_wait_for_link(pcie);
> + advk_pcie_train_link(pcie);
>
> reg = advk_readl(pcie, PCIE_CORE_CMD_STATUS_REG);
> reg |= PCIE_CORE_CMD_MEM_ACCESS_EN |
> @@ -988,6 +1046,11 @@ static int advk_pcie_probe(struct platform_device *pdev)
> }
> pcie->root_bus_nr = bus->start;
>
> + ret = of_pci_get_max_link_speed(dev->of_node);
> + if (ret < 0)
> + return ret;
Why just give up simply on DT error? Just start at gen 3 since you now
retry at lower speeds.
> + pcie->link_gen = (ret > 3) ? 3 : ret;
> +
> advk_pcie_setup_hw(pcie);
>
> advk_sw_pci_bridge_init(pcie);
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-04-24 17:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 15:38 [PATCH v3 00/12] PCI: aardvark: Fix support for Turris MOX and Compex wifi cards Pali Rohár
2020-04-24 15:38 ` [PATCH v3 01/12] PCI: aardvark: Train link immediately after enabling training Pali Rohár
2020-04-24 15:38 ` [PATCH v3 02/12] PCI: aardvark: Don't blindly enable ASPM L0s and don't write to read-only register Pali Rohár
2020-04-24 15:38 ` [PATCH v3 03/12] PCI: of: Return -ENOENT if max-link-speed property is not found Pali Rohár
2020-04-24 16:47 ` Rob Herring
2020-04-27 9:00 ` Pali Rohár
2020-04-28 15:52 ` Rob Herring
2020-04-28 16:01 ` Pali Rohár
2020-04-28 23:55 ` Marek Behun
2020-04-28 16:23 ` Bjorn Helgaas
2020-04-24 15:38 ` [PATCH v3 04/12] PCI: aardvark: Improve link training Pali Rohár
2020-04-24 17:00 ` Rob Herring [this message]
2020-04-24 18:55 ` Pali Rohár
2020-04-27 9:30 ` Pali Rohár
2020-04-24 15:38 ` [PATCH v3 05/12] PCI: aardvark: Issue PERST via GPIO Pali Rohár
2020-04-24 17:05 ` Rob Herring
2020-04-27 9:22 ` Pali Rohár
2020-04-24 15:38 ` [PATCH v3 06/12] PCI: aardvark: Add FIXME comment for PCIE_CORE_CMD_STATUS_REG access Pali Rohár
2020-04-24 15:38 ` [PATCH v3 07/12] PCI: aardvark: Add PHY support Pali Rohár
2020-04-24 15:38 ` [PATCH v3 08/12] PCI: aardvark: Replace custom macros by standard linux/pci_regs.h macros Pali Rohár
2020-04-24 18:52 ` Bjorn Helgaas
2020-04-24 15:38 ` [PATCH v3 09/12] dt-bindings: PCI: aardvark: Describe new properties Pali Rohár
2020-04-24 15:38 ` [PATCH v3 10/12] arm64: dts: marvell: armada-37xx: Set pcie_reset_pin to gpio function Pali Rohár
2020-04-24 15:38 ` [PATCH v3 11/12] arm64: dts: marvell: armada-37xx: Move PCIe comphy handle property Pali Rohár
2020-04-24 15:38 ` [PATCH v3 12/12] arm64: dts: marvell: armada-37xx: Move PCIe max-link-speed property Pali Rohár
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=CAL_JsqLTXGE4SAmbzkPJ-omusMiSoBwgF0j8HhAq7F+9w7g1wg@mail.gmail.com \
--to=robh@kernel.org \
--cc=amurray@thegoodpenguin.co.uk \
--cc=andrew@lunn.ch \
--cc=contact@xogium.me \
--cc=gregory.clement@bootlin.com \
--cc=helgaas@kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=repk@triplefau.lt \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tmn505@gmail.com \
/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).