Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Leonardo Costa <leoreis.costa@gmail.com>
Cc: hongxing.zhu@nxp.com, l.stach@pengutronix.de,
	lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
	robh@kernel.org, bhelgaas@google.com, Frank.Li@nxp.com,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com, regressions@lists.linux.dev,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	imx@lists.linux.dev, linux-kernel@vger.kernel.org,
	leonardo.costa@toradex.com, francesco@dolcini.it,
	Sherry Sun <sherry.sun@nxp.com>
Subject: Re: [REGRESSION] mainline/master: PCI link creation fails on Apalis iMX6
Date: Tue, 11 Aug 2026 16:49:00 -0500	[thread overview]
Message-ID: <20260811214900.GA763236@bhelgaas> (raw)
In-Reply-To: <bl7i3obu2clzsgeoct2a4mtfhv6typcjdqmgneropf3hpgwve6@n2m5uhlduw57>

[+cc Sherry]

On Mon, Aug 10, 2026 at 02:54:45PM -0300, Leonardo Costa wrote:
> Hello,
> 
> We are seeing a regression on Apalis iMX6 where connected PCI device
> links fail to come up at initialization, as shown below. The issue is
> not on the devices' physical connection, as they worked properly on v7.1
> and are working on other stable kernel versions.
> 
>     [    0.154243] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
>     [    0.154400] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff -> 0x0000000000
>     [    0.154439] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -> 0x0001000000
>     [    0.154553] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu 0x01f00000
>     [    0.356072] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit 4G
>     [    0.356181] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
>     [    1.364757] imx6q-pcie 1ffc000.pcie: Link failed to come up. LTSSM: POLL_CONFIG
>     [    1.365056] imx6q-pcie 1ffc000.pcie: probe with driver imx6q-pcie failed with error -110
> 
> Complete logs: https://paste.debian.net/hidden/f08cdf68
> 
> This may have been caused by commit [1], which was introduced to solve
> an issue where the Apalis iMX6 module wasn't booting, and this second
> regression went unnoticed since then.
> 
> Is it possible for all PCI changes to be reverted back to how they were
> in v7.1 before the next release?

It's *possible*, but it's tight and it would be a lot to revert.  I
think all these have been added since v7.1:

  aad953fb4eed ("PCI: imx6: Fix IMX6SX_GPR12_PCIE_TEST_POWERDOWN handling")
  610fa91d9863 ("PCI: imx6: Assert PERST# before enabling regulators")
  250eea5c06f5 ("PCI: imx6: Parse 'reset-gpios' in Root Port nodes")
  0c26b1c34d12 ("PCI: imx6: Configure REF_USE_PAD before PHY reset for i.MX95")
  9dda3f83ba67 ("PCI: imx6: Assert ref_clk_en after reference clock stabilizes on i.MX95")
  85c1fcfa740d ("PCI: imx6: Integrate new pwrctrl API")
  d4b52f83f198 ("of: Add convenience wrappers for of_map_id()")
  f71f07bee9b5 ("of: Factor arguments passed to of_map_id() into a struct")
  3567bcf0e985 ("PCI: host-generic: Move legacy DT binding fallback decision to caller of pci_host_common_parse_ports()")
  2c5768344f88 ("PCI: imx6: Move pci_pwrctrl_create_devices() to imx_pcie_probe()")
  f26b1c697a2b ("PCI: imx6: Add 'skip_pwrctrl_off' flag support")
  c2b9620359b7 ("PCI: imx6: Add runtime PM support for i.MX95")
  7678e81498e2 ("PCI: imx6: Fix i.MX6Q/DL boot hang caused by improper PHY power sequencing")

I'm hoping Richard and Sherry can resolve this issue.  I guess maybe
the config details needed to reproduce it are in
https://lore.kernel.org/all/20260811063752.GA7332@francesco-nb ?

> [1] 7678e81498e2 ("PCI: imx6: Fix i.MX6Q/DL boot hang caused by improper PHY power sequencing")
> Link: https://lore.kernel.org/all/20260629143439.361560-1-leoreis.costa@gmail.com/


      parent reply	other threads:[~2026-08-11 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 17:54 [REGRESSION] mainline/master: PCI link creation fails on Apalis iMX6 Leonardo Costa
2026-08-10 21:12 ` Francesco Dolcini
2026-08-11 21:49 ` Bjorn Helgaas [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=20260811214900.GA763236@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=festevam@gmail.com \
    --cc=francesco@dolcini.it \
    --cc=hongxing.zhu@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=kwilczynski@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=leonardo.costa@toradex.com \
    --cc=leoreis.costa@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sherry.sun@nxp.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