From: Tengfei Fan <quic_tengfan@quicinc.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
kernel@quicinc.com, linux-pci@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] PCI: qcom-ep: Add HDMA support for QCS9100 SoC
Date: Wed, 10 Jul 2024 15:18:36 +0800 [thread overview]
Message-ID: <417ff30e-87d9-4816-addc-943f96ec64ac@quicinc.com> (raw)
In-Reply-To: <20240709162621.GA175973@bhelgaas>
On 7/10/2024 12:26 AM, Bjorn Helgaas wrote:
> On Tue, Jul 09, 2024 at 10:53:44PM +0800, Tengfei Fan wrote:
>> QCS9100 SoC supports the new Hyper DMA (HDMA) DMA Engine inside the DWC IP,
>> so add support for it by passing the mapping format and the number of
>> read/write channels count.
>>
>> The PCIe EP controller used on this SoC is of version 1.34.0, so a separate
>> config struct is introduced for the sake of enabling HDMA conditionally.
>
> This patch doesn't add a new config struct.
Thank you for pointing out this. I will remove this commit message in
the next version patch series.
>
>> It should be noted that for the eDMA support (predecessor of HDMA), there
>> are no mapping format and channels count specified. That is because eDMA
>> supports auto detection of both parameters, whereas HDMA doesn't.
>>
>> QCS9100 is drived from SA8775p. Currently, both the QCS9100 and SA8775p
>> platform use non-SCMI resource. In the future, the SA8775p platform will
>> move to use SCMI resources and it will have new sa8775p-related device
>> tree. Consequently, introduce "qcom,qcs9100-pcie-ep" to the PCIe device
>> match table.
>
> This series doesn't add the new SCMI stuff you mention. It sounds
> like this should be deferred and added when you actually move to using
> SCMI resources.
This patch shouldn't be deferred.
This patch is used to support QSC9100. QCS9100 uses non-SCMI resources,
so there is nothing related to SCMI in this patch.
Only SA8775p will move to use SCMI resources in the future.
>
>> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
>> ---
>> drivers/pci/controller/dwc/pcie-qcom-ep.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-qcom-ep.c b/drivers/pci/controller/dwc/pcie-qcom-ep.c
>> index 236229f66c80..e2775f4ca7ee 100644
>> --- a/drivers/pci/controller/dwc/pcie-qcom-ep.c
>> +++ b/drivers/pci/controller/dwc/pcie-qcom-ep.c
>> @@ -904,6 +904,7 @@ static const struct qcom_pcie_ep_cfg cfg_1_34_0 = {
>> };
>>
>> static const struct of_device_id qcom_pcie_ep_match[] = {
>> + { .compatible = "qcom,qcs9100-pcie-ep", .data = &cfg_1_34_0},
>> { .compatible = "qcom,sa8775p-pcie-ep", .data = &cfg_1_34_0},
>> { .compatible = "qcom,sdx55-pcie-ep", },
>> { .compatible = "qcom,sm8450-pcie-ep", },
>>
>> --
>> 2.25.1
>>
--
Thx and BRs,
Tengfei Fan
next prev parent reply other threads:[~2024-07-10 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 14:53 [PATCH v2 0/2] PCI: qcom-ep: Add QCS9100 PCIe ep compatible Tengfei Fan
2024-07-09 14:53 ` [PATCH v2 1/2] dt-bindings: PCI: qcom-ep: Add support for QCS9100 SoC Tengfei Fan
2024-07-09 16:28 ` Bjorn Helgaas
2024-07-10 7:09 ` Tengfei Fan
2024-07-10 10:31 ` Aiqun Yu (Maria)
2024-07-29 10:08 ` Tengfei Fan
2024-07-09 14:53 ` [PATCH v2 2/2] PCI: qcom-ep: Add HDMA " Tengfei Fan
2024-07-09 16:26 ` Bjorn Helgaas
2024-07-10 7:18 ` Tengfei Fan [this message]
2024-07-10 10:40 ` Aiqun Yu (Maria)
2024-07-29 10:08 ` Tengfei Fan
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=417ff30e-87d9-4816-addc-943f96ec64ac@quicinc.com \
--to=quic_tengfan@quicinc.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=kernel@quicinc.com \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--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