From: Bjorn Helgaas <helgaas@kernel.org>
To: Florian Eckert <fe@dev.tdt.de>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Johan Hovold" <johan+linaro@kernel.org>,
"Sajid Dalvi" <sdalvi@google.com>,
"Ajay Agarwal" <ajayagarwal@google.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Eckert.Florian@googlemail.com,
ms@dev.tdt.de
Subject: Re: [PATCH v5 5/7] PCI: intel-gw: Add start_link callback function
Date: Tue, 12 May 2026 15:49:21 -0500 [thread overview]
Message-ID: <20260512204921.GA243550@bhelgaas> (raw)
In-Reply-To: <20260417-pcie-intel-gw-v5-5-0a2b933fe04f@dev.tdt.de>
On Fri, Apr 17, 2026 at 10:35:49AM +0200, Florian Eckert wrote:
> The pcie-intel-gw driver has no start_link callback function. This commit
> adds the missing callback function so that the driver works again and does
> not abort with the following error messages during probing.
>
> [ 2.512015] intel-gw-pcie d1000000.pcie: host bridge /soc/pcie@d1000000 ranges:
> [ 2.517868] intel-gw-pcie d1000000.pcie: MEM 0x00dc000000..0x00ddffffff -> 0x00dc000000
> [ 2.528450] intel-combo-phy d0c00000.combo-phy: Set combo mode: combophy[1]: mode: PCIe single lane mode
> [ 2.551619] intel-gw-pcie d1000000.pcie: No outbound iATU found
> [ 2.556060] intel-gw-pcie d1000000.pcie: Cannot initialize host
> [ 2.561901] intel-gw-pcie d1000000.pcie: probe with driver intel-gw-pcie failed with error -22
> [ 2.571041] intel-gw-pcie c1100000.pcie: host bridge /soc/pcie@c1100000 ranges:
> [ 2.577736] intel-gw-pcie c1100000.pcie: MEM 0x00ce000000..0x00cfffffff -> 0x00ce000000
> [ 2.588299] intel-combo-phy c0c00000.combo-phy: Set combo mode: combophy[3]: mode: PCIe single lane mode
> [ 2.611471] intel-gw-pcie c1100000.pcie: No outbound iATU found
> [ 2.615934] intel-gw-pcie c1100000.pcie: Cannot initialize host
> [ 2.621759] intel-gw-pcie c1100000.pcie: probe with driver intel-gw-pcie failed with error -22
>
> Fixes: c5097b9869a1 ("Revert "PCI: dwc: Wait for link up only if link is started"")
> Fixes: da56a1bfbab5 ("PCI: dwc: Wait for link up only if link is started")
This applied already; I just want to understand this better for
writing the merge commit log.
da56a1bfbab5 and c5097b9869a1 date from v6.5 in 2023. I guess this
driver has been completely broken since then and nobody noticed?
Thanks for fixing this up. I assume that means there is somebody
actually using this driver, even though nobody cares quite enough to
maintain it?
next prev parent reply other threads:[~2026-05-12 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 8:35 [PATCH v5 0/7] PCI: intel-gw: Fixes to make the driver working again Florian Eckert
2026-04-17 8:35 ` [PATCH v5 1/7] MAINTAINERS: Remove bouncing intel-gw maintainer Florian Eckert
2026-05-11 23:26 ` Bjorn Helgaas
2026-04-17 8:35 ` [PATCH v5 2/7] PCI: intel-gw: Remove unused define Florian Eckert
2026-04-17 8:35 ` [PATCH v5 3/7] PCI: intel-gw: Move interrupt enable to own function Florian Eckert
2026-04-17 8:35 ` [PATCH v5 4/7] PCI: intel-gw: Enable clock before phy init Florian Eckert
2026-04-17 8:35 ` [PATCH v5 5/7] PCI: intel-gw: Add start_link callback function Florian Eckert
2026-05-12 20:49 ` Bjorn Helgaas [this message]
2026-05-13 6:56 ` Florian Eckert
2026-04-17 8:35 ` [PATCH v5 6/7] PCI: intel-gw: Move driver atu base assignment to probe function Florian Eckert
2026-04-17 8:35 ` [PATCH v5 7/7] dt-bindings: PCI: intel,lgm-pcie: Add atu resource Florian Eckert
2026-04-21 19:04 ` Rob Herring (Arm)
2026-05-06 6:45 ` [PATCH v5 0/7] PCI: intel-gw: Fixes to make the driver working again Florian Eckert
2026-05-07 17:10 ` Manivannan Sadhasivam
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=20260512204921.GA243550@bhelgaas \
--to=helgaas@kernel.org \
--cc=Eckert.Florian@googlemail.com \
--cc=ajayagarwal@google.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fe@dev.tdt.de \
--cc=johan+linaro@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=ms@dev.tdt.de \
--cc=robh@kernel.org \
--cc=sdalvi@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.