Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Ziyue Zhang <quic_ziyuzhan@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <vkoul@kernel.org>, <kishon@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<dmitry.baryshkov@linaro.org>, <neil.armstrong@linaro.org>,
	<abel.vesa@linaro.org>, <manivannan.sadhasivam@linaro.org>,
	<lpieralisi@kernel.org>, <kw@linux.com>, <bhelgaas@google.com>,
	<andersson@kernel.org>, <konradybcio@kernel.org>,
	<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<linux-pci@vger.kernel.org>, <quic_qianyu@quicinc.com>,
	<quic_krichai@quicinc.com>, <quic_vbadigan@quicinc.com>
Subject: Re: [PATCH v4 5/5] PCI: qcom: Add support for QCS615 SoC
Date: Mon, 12 May 2025 17:03:10 +0800	[thread overview]
Message-ID: <37b5681b-ebf5-4956-8111-b53383dce755@quicinc.com> (raw)
In-Reply-To: <20250507-competent-meek-prawn-72badf@kuoka>


On 5/7/2025 1:18 PM, Krzysztof Kozlowski wrote:
> On Wed, May 07, 2025 at 11:15:59AM GMT, Ziyue Zhang wrote:
>> Add the compatible and the driver data for QCS615 PCIe controller.
>> There is only one controller instance found on this platform, which
>> is capable of up to 8.0GT/s.
>> The version of the controller is 1.38.0 which is compatible with 1.9.0
>> config.
>>
>> Signed-off-by: Krishna chaitanya chundru <quic_krichai@quicinc.com>
>> Signed-off-by: Ziyue Zhang <quic_ziyuzhan@quicinc.com>
>> ---
>>   drivers/pci/controller/dwc/pcie-qcom.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
>> index dc98ae63362d..0ed934b0d1be 100644
>> --- a/drivers/pci/controller/dwc/pcie-qcom.c
>> +++ b/drivers/pci/controller/dwc/pcie-qcom.c
>> @@ -1862,6 +1862,7 @@ static const struct of_device_id qcom_pcie_match[] = {
>>   	{ .compatible = "qcom,pcie-sm8450-pcie1", .data = &cfg_1_9_0 },
>>   	{ .compatible = "qcom,pcie-sm8550", .data = &cfg_1_9_0 },
>>   	{ .compatible = "qcom,pcie-x1e80100", .data = &cfg_sc8280xp },
>> +	{ .compatible = "qcom,qcs615-pcie", .data = &cfg_1_9_0 },
> Why? It's compatible with other entries, so why adding redundant entry
> here?
>
> Best regards,
> Krzysztof

Hi Krzysztof

If I use the compatible entry for qcs615 in the driver, do I need to
add qcom,qcs615-pcie to qcom,pcie-sm8550.yaml, or should I create a new
YAML file specifically for qcs615-pcie? Given that the PCIe cores on
qcs615 and sm8550 require different clocks, is it acceptable to combine
them in qcom,pcie-sm8550.yaml?

BRs
Ziyue


  reply	other threads:[~2025-05-12  9:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07  3:15 [PATCH v4 0/5] pci: qcom: Add QCS615 PCIe support Ziyue Zhang
2025-05-07  3:15 ` [PATCH v4 1/5] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Update pcie phy bindings for QCS615 Ziyue Zhang
2025-05-07  5:12   ` Krzysztof Kozlowski
2025-05-07  3:15 ` [PATCH v4 2/5] dt-bindings: PCI: qcom: Document the QCS615 PCIe Controller Ziyue Zhang
2025-05-07  5:17   ` Krzysztof Kozlowski
2025-05-12  8:16     ` Ziyue Zhang
2025-05-12  9:26       ` Krzysztof Kozlowski
2025-05-07  3:15 ` [PATCH v4 3/5] arm64: dts: qcom: qcs615: enable pcie Ziyue Zhang
2025-05-08 14:47   ` Konrad Dybcio
2025-05-07  3:15 ` [PATCH v4 4/5] arm64: dts: qcom: qcs615-ride: Enable PCIe interface Ziyue Zhang
2025-05-07  3:15 ` [PATCH v4 5/5] PCI: qcom: Add support for QCS615 SoC Ziyue Zhang
2025-05-07  5:18   ` Krzysztof Kozlowski
2025-05-12  9:03     ` Ziyue Zhang [this message]
2025-05-07 15:41 ` [PATCH v4 0/5] pci: qcom: Add QCS615 PCIe support Rob Herring (Arm)

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=37b5681b-ebf5-4956-8111-b53383dce755@quicinc.com \
    --to=quic_ziyuzhan@quicinc.com \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=kishon@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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=linux-phy@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_krichai@quicinc.com \
    --cc=quic_qianyu@quicinc.com \
    --cc=quic_vbadigan@quicinc.com \
    --cc=robh@kernel.org \
    --cc=vkoul@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