From: Shawn Guo <shawn.guo@freescale.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: <bhelgaas@google.com>, <r65037@freescale.com>,
<linux-pci@vger.kernel.org>, <marex@denx.de>,
<l.stach@pengutronix.de>, <tharvey@gateworks.com>,
<d.mueller@elsoft.ch>,
Fabio Estevam <fabio.estevam@freescale.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] PCI: imx6: fix boot hang when link already enabled
Date: Thu, 7 Aug 2014 10:12:47 +0800 [thread overview]
Message-ID: <20140807021246.GL2167@dragon> (raw)
In-Reply-To: <1407356079-28908-1-git-send-email-festevam@gmail.com>
On Wed, Aug 06, 2014 at 05:14:39PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> This fixes a boot hang observed when the bootloader
> already enabled the PCIe link for it's own use. The
> fundamental problem is that Freescale forgot to wire
> up the core reset, so software doesn't have a sane way
> to get the core into a defined state.
>
> According to the DW PCIe core reference manual configuration
> of the core may only happen when the LTSSM is disabled, so
> this is one of the first things we do. Apparently this isn't
> safe to do when the LTSSM is in any other state than
> "detect" as we observe an instant machine hang when trying to
> do so while the link is already up.
>
> As a workaround force LTSSM into detect state right before
> hitting the disable switch.
>
> Tested on a mx6qsabresd board with PCI driver enabled in the
> bootloader and also with PCI driver disabled in the bootloader.
> The kernel boots succesfully on both cases now.
>
> Cc: <stable@vger.kernel.org> # 3.16
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
I believe Lucas already had a new version of his patch.
http://thread.gmane.org/gmane.linux.kernel.pci/33712/focus=33711
Shawn
> ---
> drivers/pci/host/pci-imx6.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/pci/host/pci-imx6.c b/drivers/pci/host/pci-imx6.c
> index a568efa..2fa6d3a 100644
> --- a/drivers/pci/host/pci-imx6.c
> +++ b/drivers/pci/host/pci-imx6.c
> @@ -49,6 +49,9 @@ struct imx6_pcie {
>
> /* PCIe Port Logic registers (memory-mapped) */
> #define PL_OFFSET 0x700
> +#define PCIE_PL_PFLR (PL_OFFSET + 0x08)
> +#define PCIE_PL_PFLR_LINK_STATE_MASK (0x3f << 16)
> +#define PCIE_PL_PFLR_FORCE_LINK (1 << 15)
> #define PCIE_PHY_DEBUG_R0 (PL_OFFSET + 0x28)
> #define PCIE_PHY_DEBUG_R1 (PL_OFFSET + 0x2c)
> #define PCIE_PHY_DEBUG_R1_XMLH_LINK_IN_TRAINING (1 << 29)
> @@ -214,7 +217,19 @@ static int imx6q_pcie_abort_handler(unsigned long addr,
> static int imx6_pcie_assert_core_reset(struct pcie_port *pp)
> {
> struct imx6_pcie *imx6_pcie = to_imx6_pcie(pp);
> + u32 val;
> +
> + regmap_read(imx6_pcie->iomuxc_gpr, IOMUXC_GPR12, &val);
>
> + if (val & IMX6Q_GPR12_PCIE_CTL_2) {
> + val = readl(pp->dbi_base + PCIE_PL_PFLR);
> + val &= ~PCIE_PL_PFLR_LINK_STATE_MASK;
> + val |= PCIE_PL_PFLR_FORCE_LINK;
> + writel(val, pp->dbi_base + PCIE_PL_PFLR);
> +
> + regmap_update_bits(imx6_pcie->iomuxc_gpr, IOMUXC_GPR12,
> + IMX6Q_GPR12_PCIE_CTL_2, 0 << 10);
> + }
> regmap_update_bits(imx6_pcie->iomuxc_gpr, IOMUXC_GPR1,
> IMX6Q_GPR1_PCIE_TEST_PD, 1 << 18);
> regmap_update_bits(imx6_pcie->iomuxc_gpr, IOMUXC_GPR1,
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-08-07 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 20:14 [PATCH] PCI: imx6: fix boot hang when link already enabled Fabio Estevam
2014-08-07 2:12 ` Shawn Guo [this message]
2014-08-07 2:32 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2014-07-21 18:12 Lucas Stach
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=20140807021246.GL2167@dragon \
--to=shawn.guo@freescale.com \
--cc=bhelgaas@google.com \
--cc=d.mueller@elsoft.ch \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.org \
--cc=marex@denx.de \
--cc=r65037@freescale.com \
--cc=stable@vger.kernel.org \
--cc=tharvey@gateworks.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).