public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Ron Economos <re@w6rz.net>
Cc: bhelgaas@google.com, rishna.chundru@oss.qualcomm.com,
	mani@kernel.org, helgaas@kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-riscv <linux-riscv@lists.infradead.org>,
	Paul Walmsley <pjw@kernel.org>,
	Greentime Hu <greentime.hu@sifive.com>,
	Samuel Holland <samuel.holland@sifive.com>,
	Conor Dooley <conor@kernel.org>,
	regressions@lists.linux.dev
Subject: Re: SiFive FU740 PCI driver fails on 6.18-rc1
Date: Mon, 13 Oct 2025 16:28:01 -0500	[thread overview]
Message-ID: <20251013212801.GA865570@bhelgaas> (raw)
In-Reply-To: <eac81c57-1164-4d74-a1b4-6f353c577731@w6rz.net>

[+cc FU740 driver folks, Conor, regressions]

On Mon, Oct 13, 2025 at 12:14:54AM -0700, Ron Economos wrote:
> The SiFive FU740 PCI driver fails on the HiFive Unmatched board with Linux
> 6.18-rc1. The error message is:
> 
> [    3.166624] fu740-pcie e00000000.pcie: host bridge /soc/pcie@e00000000
> ranges:
> [    3.166706] fu740-pcie e00000000.pcie:       IO
> 0x0060080000..0x006008ffff -> 0x0060080000
> [    3.166767] fu740-pcie e00000000.pcie:      MEM
> 0x0060090000..0x007fffffff -> 0x0060090000
> [    3.166805] fu740-pcie e00000000.pcie:      MEM
> 0x2000000000..0x3fffffffff -> 0x2000000000
> [    3.166950] fu740-pcie e00000000.pcie: ECAM at [mem
> 0xdf0000000-0xdffffffff] for [bus 00-ff]
> [    3.579500] fu740-pcie e00000000.pcie: No iATU regions found
> [    3.579552] fu740-pcie e00000000.pcie: Failed to configure iATU in ECAM
> mode
> [    3.579655] fu740-pcie e00000000.pcie: probe with driver fu740-pcie
> failed with error -22
> 
> The normal message (on Linux 6.17.2) is:
> 
> [    3.381487] fu740-pcie e00000000.pcie: host bridge /soc/pcie@e00000000
> ranges:
> [    3.381584] fu740-pcie e00000000.pcie:       IO
> 0x0060080000..0x006008ffff -> 0x0060080000
> [    3.381682] fu740-pcie e00000000.pcie:      MEM
> 0x0060090000..0x007fffffff -> 0x0060090000
> [    3.381724] fu740-pcie e00000000.pcie:      MEM
> 0x2000000000..0x3fffffffff -> 0x2000000000
> [    3.484809] fu740-pcie e00000000.pcie: iATU: unroll T, 8 ob, 8 ib, align
> 4K, limit 4096G
> [    3.683678] fu740-pcie e00000000.pcie: PCIe Gen.1 x8 link up
> [    3.883674] fu740-pcie e00000000.pcie: PCIe Gen.3 x8 link up
> [    3.987678] fu740-pcie e00000000.pcie: PCIe Gen.3 x8 link up
> [    3.988164] fu740-pcie e00000000.pcie: PCI host bridge to bus 0000:00
> 
> Reverting the following commits solves the issue.
> 
> 0da48c5b2fa731b21bc523c82d927399a1e508b0 PCI: dwc: Support ECAM mechanism by
> enabling iATU 'CFG Shift Feature'
> 
> 4660e50cf81800f82eeecf743ad1e3e97ab72190 PCI: qcom: Prepare for the DWC ECAM
> enablement
> 
> f6fd357f7afbeb34a633e5688a23b9d7eb49d558 PCI: dwc: Prepare the driver for
> enabling ECAM mechanism using iATU 'CFG Shift Feature'

As Conor pointed out, we can't fix a code regression with a DT change.

#regzbot introduced: f6fd357f7afb ("PCI: dwc: Prepare the driver for enabling ECAM mechanism using iATU 'CFG Shift Feature'")

  parent reply	other threads:[~2025-10-13 21:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13  7:14 SiFive FU740 PCI driver fails on 6.18-rc1 Ron Economos
2025-10-13  8:19 ` Krishna Chaitanya Chundru
2025-10-13 14:51   ` Conor Dooley
2025-10-13 21:28 ` Bjorn Helgaas [this message]
2025-10-14  5:20   ` Krishna Chaitanya Chundru
2025-10-14  5:26     ` Ron Economos
2025-10-14  5:36       ` Krishna Chaitanya Chundru
2025-10-14  5:52         ` Ron Economos
2025-10-14 16:25           ` Manivannan Sadhasivam
2025-10-14 22:41             ` Ron Economos
2025-10-15 14:03               ` Manivannan Sadhasivam
2025-10-17 11:43                 ` Krishna Chaitanya Chundru
2025-10-17 14:21                   ` Ron Economos
2025-10-17 15:17                     ` Manivannan Sadhasivam
2025-10-28 22:38                     ` Bjorn Helgaas

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=20251013212801.GA865570@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor@kernel.org \
    --cc=greentime.hu@sifive.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=pjw@kernel.org \
    --cc=re@w6rz.net \
    --cc=regressions@lists.linux.dev \
    --cc=rishna.chundru@oss.qualcomm.com \
    --cc=samuel.holland@sifive.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