From: Praveenkumar I <quic_ipkumar@quicinc.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
<george.moussalem@outlook.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Nitheesh Sekar" <quic_nsekar@quicinc.com>,
"Varadarajan Narayanan" <quic_varada@quicinc.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org,
20250317100029.881286-2-quic_varada@quicinc.com,
"Sricharan R" <quic_srichara@quicinc.com>
Subject: Re: [PATCH v6 5/6] arm64: dts: qcom: ipq5018: Add PCIe related nodes
Date: Mon, 24 Mar 2025 16:48:34 +0530 [thread overview]
Message-ID: <6fa2bd30-762b-4a3a-b94f-8798c027764a@quicinc.com> (raw)
In-Reply-To: <a4n3w62bg6x2iux4z7enu3po56hr5pcavjfmvtzdcwv2w4ptrr@ssvfdrltfg5y>
On 3/24/2025 1:26 PM, Manivannan Sadhasivam wrote:
> On Fri, Mar 21, 2025 at 04:14:43PM +0400, George Moussalem via B4 Relay wrote:
>> From: Nitheesh Sekar<quic_nsekar@quicinc.com>
>>
>> Add phy and controller nodes for a 2-lane Gen2 and
> Controller is Gen 3 capable but you are limiting it to Gen 2.
>
>> a 1-lane Gen2 PCIe bus. IPQ5018 has 8 MSI SPI interrupts and
>> one global interrupt.
>>
>> Signed-off-by: Nitheesh Sekar<quic_nsekar@quicinc.com>
>> Signed-off-by: Sricharan R<quic_srichara@quicinc.com>
>> Signed-off-by: George Moussalem<george.moussalem@outlook.com>
> One comment below. With that addressed,
>
> Reviewed-by: Manivannan Sadhasivam<manivannan.sadhasivam@linaro.org>
>
>> ---
>> arch/arm64/boot/dts/qcom/ipq5018.dtsi | 234 +++++++++++++++++++++++++++++++++-
>> 1 file changed, 232 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/ipq5018.dtsi b/arch/arm64/boot/dts/qcom/ipq5018.dtsi
>> index 8914f2ef0bc4..d08034b57e80 100644
>> --- a/arch/arm64/boot/dts/qcom/ipq5018.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/ipq5018.dtsi
>> @@ -147,6 +147,40 @@ usbphy0: phy@5b000 {
>> status = "disabled";
>> };
>>
>> + pcie1_phy: phy@7e000{
>> + compatible = "qcom,ipq5018-uniphy-pcie-phy";
>> + reg = <0x0007e000 0x800>;
>> +
>> + clocks = <&gcc GCC_PCIE1_PIPE_CLK>;
>> +
>> + resets = <&gcc GCC_PCIE1_PHY_BCR>,
>> + <&gcc GCC_PCIE1PHY_PHY_BCR>;
>> +
>> + #clock-cells = <0>;
>> + #phy-cells = <0>;
>> +
>> + num-lanes = <1>;
>> +
>> + status = "disabled";
>> + };
>> +
>> + pcie0_phy: phy@86000{
>> + compatible = "qcom,ipq5018-uniphy-pcie-phy";
>> + reg = <0x00086000 0x800>;
>> +
>> + clocks = <&gcc GCC_PCIE0_PIPE_CLK>;
>> +
>> + resets = <&gcc GCC_PCIE0_PHY_BCR>,
>> + <&gcc GCC_PCIE0PHY_PHY_BCR>;
>> +
>> + #clock-cells = <0>;
>> + #phy-cells = <0>;
>> +
>> + num-lanes = <2>;
>> +
>> + status = "disabled";
>> + };
>> +
>> tlmm: pinctrl@1000000 {
>> compatible = "qcom,ipq5018-tlmm";
>> reg = <0x01000000 0x300000>;
>> @@ -170,8 +204,8 @@ gcc: clock-controller@1800000 {
>> reg = <0x01800000 0x80000>;
>> clocks = <&xo_board_clk>,
>> <&sleep_clk>,
>> - <0>,
>> - <0>,
>> + <&pcie0_phy>,
>> + <&pcie1_phy>,
>> <0>,
>> <0>,
>> <0>,
>> @@ -387,6 +421,202 @@ frame@b128000 {
>> status = "disabled";
>> };
>> };
>> +
>> + pcie1: pcie@80000000 {
>> + compatible = "qcom,pcie-ipq5018";
>> + reg = <0x80000000 0xf1d>,
>> + <0x80000f20 0xa8>,
>> + <0x80001000 0x1000>,
>> + <0x00078000 0x3000>,
>> + <0x80100000 0x1000>,
>> + <0x0007b000 0x1000>;
>> + reg-names = "dbi",
>> + "elbi",
>> + "atu",
>> + "parf",
>> + "config",
>> + "mhi";
>> + device_type = "pci";
>> + linux,pci-domain = <0>;
>> + bus-range = <0x00 0xff>;
>> + num-lanes = <1>;
>> + max-link-speed = <2>;
> This still needs some justification. If Qcom folks didn't reply, atleast move
> this to board dts with a comment saying that the link is not coming up with
> Gen3.
>
> - Mani
The IPQ5018 PCIe controller can support Gen3, but the PCIe phy is
limited Gen2 and does not supported Gen3.
Hence, it is restricted using the DTSI property.
--
Thanks,
Praveenkumar
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-03-24 11:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 12:14 [PATCH v6 0/6] Enable IPQ5018 PCI support George Moussalem via B4 Relay
2025-03-21 12:14 ` [PATCH v6 1/6] dt-bindings: phy: qcom: uniphy-pcie: Add ipq5018 compatible George Moussalem via B4 Relay
2025-03-22 20:16 ` Rob Herring (Arm)
2025-03-21 12:14 ` [PATCH v6 2/6] phy: qualcomm: qcom-uniphy-pcie 28LP add support for IPQ5018 George Moussalem via B4 Relay
2025-03-21 14:10 ` Dmitry Baryshkov
2025-03-21 12:14 ` [PATCH v6 3/6] dt-bindings: PCI: qcom: Add IPQ5018 SoC George Moussalem via B4 Relay
2025-03-24 7:50 ` Krzysztof Kozlowski
2025-03-24 7:52 ` Manivannan Sadhasivam
2025-03-21 12:14 ` [PATCH v6 4/6] PCI: qcom: Add support for IPQ5018 George Moussalem via B4 Relay
2025-03-21 12:14 ` [PATCH v6 5/6] arm64: dts: qcom: ipq5018: Add PCIe related nodes George Moussalem via B4 Relay
2025-03-21 14:10 ` Dmitry Baryshkov
2025-03-24 7:56 ` Manivannan Sadhasivam
2025-03-24 11:18 ` Praveenkumar I [this message]
2025-03-24 11:36 ` Dmitry Baryshkov
2025-03-24 19:40 ` Konrad Dybcio
2025-03-25 16:53 ` Manivannan Sadhasivam
2025-03-26 7:41 ` Praveenkumar I
2025-03-27 17:28 ` Manivannan Sadhasivam
2025-03-21 12:14 ` [PATCH v6 6/6] arm64: dts: qcom: ipq5018: Enable PCIe George Moussalem via B4 Relay
2025-03-21 14:13 ` Dmitry Baryshkov
2025-03-24 8:06 ` George Moussalem
2025-03-24 19:38 ` Konrad Dybcio
2025-03-24 7:58 ` Manivannan Sadhasivam
2025-03-24 19:39 ` Konrad Dybcio
2025-03-21 15:05 ` [PATCH v6 0/6] Enable IPQ5018 PCI support Rob Herring (Arm)
2025-03-24 7:47 ` Krzysztof Kozlowski
2025-03-25 7:55 ` George Moussalem
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=6fa2bd30-762b-4a3a-b94f-8798c027764a@quicinc.com \
--to=quic_ipkumar@quicinc.com \
--cc=20250317100029.881286-2-quic_varada@quicinc.com \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.moussalem@outlook.com \
--cc=kishon@kernel.org \
--cc=konradybcio@kernel.org \
--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=linux-phy@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_nsekar@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@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