From: Manivannan Sadhasivam <mani@kernel.org>
To: cros-qcom-dts-watchers@chromium.org,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
quic_vbadigan@quicinc.com, quic_mrana@quicinc.com,
quic_vpernami@quicinc.com, mmareddy@quicinc.com,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: (subset) [PATCH v8 0/5] PCI: dwc: Add ECAM support with iATU configuration
Date: Mon, 01 Sep 2025 19:12:31 +0530 [thread overview]
Message-ID: <175673415116.10403.13836370686011733892.b4-ty@kernel.org> (raw)
In-Reply-To: <20250828-ecam_v4-v8-0-92a30e0fa02d@oss.qualcomm.com>
On Thu, 28 Aug 2025 13:04:21 +0530, Krishna Chaitanya Chundru wrote:
> The current implementation requires iATU for every configuration
> space access which increases latency & cpu utilization.
>
> Designware databook 5.20a, section 3.10.10.3 says about CFG Shift Feature,
> which shifts/maps the BDF (bits [31:16] of the third header DWORD, which
> would be matched against the Base and Limit addresses) of the incoming
> CfgRd0/CfgWr0 down to bits[27:12]of the translated address.
>
> [...]
Applied, thanks!
[2/5] PCI: dwc: Add support for ELBI resource mapping
commit: d39e0103e38f9889271a77a837b6179b42d6730d
[3/5] PCI: dwc: qcom: Switch to dwc ELBI resource mapping
commit: 6955a13b1349376a00ebca80d1a8e2960de3fb0f
[4/5] PCI: dwc: Add ECAM support with iATU configuration
commit: 0c959f675ce0338f3bee2636437bce4d5713ea03
[5/5] PCI: qcom: Add support for ECAM feature
commit: 0bba488d552dccda4b803fa4b5d4d5d3029d601d
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2025-09-01 13:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 7:34 [PATCH v8 0/5] PCI: dwc: Add ECAM support with iATU configuration Krishna Chaitanya Chundru
2025-08-28 7:34 ` [PATCH v8 1/5] arm64: dts: qcom: sc7280: Increase config size to 256MB for ECAM feature Krishna Chaitanya Chundru
2025-08-28 7:34 ` [PATCH v8 2/5] PCI: dwc: Add support for ELBI resource mapping Krishna Chaitanya Chundru
2025-08-31 11:48 ` Manivannan Sadhasivam
2025-09-01 6:55 ` Krishna Chaitanya Chundru
2025-09-01 9:07 ` Manivannan Sadhasivam
2025-09-01 13:44 ` Manivannan Sadhasivam
2025-09-01 13:48 ` Manivannan Sadhasivam
2025-09-03 18:56 ` Bjorn Helgaas
2025-08-28 7:34 ` [PATCH v8 3/5] PCI: dwc: qcom: Switch to dwc " Krishna Chaitanya Chundru
2025-09-03 19:14 ` Bjorn Helgaas
2025-08-28 7:34 ` [PATCH v8 4/5] PCI: dwc: Add ECAM support with iATU configuration Krishna Chaitanya Chundru
2025-09-01 13:52 ` Manivannan Sadhasivam
2025-09-03 20:10 ` Bjorn Helgaas
2025-08-28 7:34 ` [PATCH v8 5/5] PCI: qcom: Add support for ECAM feature Krishna Chaitanya Chundru
2025-09-03 19:57 ` Bjorn Helgaas
2025-09-03 20:12 ` Bjorn Helgaas
2025-09-01 13:42 ` Manivannan Sadhasivam [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=175673415116.10403.13836370686011733892.b4-ty@kernel.org \
--to=mani@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=jingoohan1@gmail.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--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=mmareddy@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=quic_vpernami@quicinc.com \
--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;
as well as URLs for NNTP newsgroup(s).