From: Bjorn Helgaas <helgaas@kernel.org>
To: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, "Ron Economos" <re@w6rz.net>
Subject: Re: [PATCH 0/2] PCI: dwc: Fix ECAM enablement when used with vendor drivers
Date: Fri, 17 Oct 2025 16:58:17 -0500 [thread overview]
Message-ID: <20251017215817.GA1047160@bhelgaas> (raw)
In-Reply-To: <20251017-ecam_fix-v1-0-f6faa3d0edf3@oss.qualcomm.com>
On Fri, Oct 17, 2025 at 05:10:52PM +0530, Krishna Chaitanya Chundru wrote:
> This series addresses issues with ECAM enablement in the DesignWare PCIe
> host controller when used with vendor drivers that rely on the DBI base
> for internal accesses.
>
> The first patch fixes the ECAM logic by introducing a custom PCI ops
> implementation that avoids overwriting the DBI base, ensuring compatibility
> with vendor drivers that expect a stable DBI address.
>
> The second patch reverts Qualcomm-specific ECAM preparation logic that
> is no longer needed due to the updated design.
>
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> ---
> Krishna Chaitanya Chundru (2):
> PCI: dwc: Fix ECAM enablement when used with vendor drivers
> PCI: dwc: qcom: Revert "PCI: qcom: Prepare for the DWC ECAM enablement"
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 28 ++++++++--
> drivers/pci/controller/dwc/pcie-qcom.c | 68 -----------------------
> 2 files changed, 24 insertions(+), 72 deletions(-)
> ---
> base-commit: 9b332cece987ee1790b2ed4c989e28162fa47860
> change-id: 20251015-ecam_fix-641d1d5ed71d
I hope we can remove the assumption that the root bus is bus 0, but in
the meantime I added these to pci/for-linus so we can build and test
them.
They're after the pci-v6.18-fixes-2 tag I just asked Linus to pull, so
they won't be in v6.18-rc2, but should make it for -rc3.
Bjorn
next prev parent reply other threads:[~2025-10-17 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 11:40 [PATCH 0/2] PCI: dwc: Fix ECAM enablement when used with vendor drivers Krishna Chaitanya Chundru
2025-10-17 11:40 ` [PATCH 1/2] " Krishna Chaitanya Chundru
2025-10-17 14:24 ` Ron Economos
2025-10-17 19:10 ` Bjorn Helgaas
2025-10-18 3:09 ` Manivannan Sadhasivam
2025-10-18 9:25 ` Krishna Chaitanya Chundru
2025-10-18 9:30 ` Krishna Chaitanya Chundru
2025-10-21 2:25 ` Manivannan Sadhasivam
2025-10-21 12:12 ` Krishna Chaitanya Chundru
2025-10-21 15:57 ` Bjorn Helgaas
2025-10-17 11:40 ` [PATCH 2/2] PCI: dwc: qcom: Revert "PCI: qcom: Prepare for the DWC ECAM enablement" Krishna Chaitanya Chundru
2025-10-17 21:58 ` Bjorn Helgaas [this message]
2025-10-18 9:26 ` [PATCH 0/2] PCI: dwc: Fix ECAM enablement when used with vendor drivers Krishna Chaitanya Chundru
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=20251017215817.GA1047160@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=re@w6rz.net \
--cc=robh@kernel.org \
/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