From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: <bhelgaas@google.com>, <lpieralisi@kernel.org>, <kw@linux.com>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<vkoul@kernel.org>, <kishon@kernel.org>, <andersson@kernel.org>,
<konradybcio@kernel.org>, <p.zabel@pengutronix.de>,
<dmitry.baryshkov@linaro.org>, <quic_nsekar@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-phy@lists.infradead.org>, <robimarko@gmail.com>
Subject: Re: [PATCH V2 4/6] PCI: qcom: Add support for IPQ5018
Date: Wed, 4 Sep 2024 22:51:30 +0530 [thread overview]
Message-ID: <ea8ccb1e-2344-4c35-8a95-7b3f1fe23e08@quicinc.com> (raw)
In-Reply-To: <20240830083852.cwjc6skgypva6u6u@thinkpad>
On 8/30/2024 2:08 PM, Manivannan Sadhasivam wrote:
> On Tue, Aug 27, 2024 at 10:27:55AM +0530, Sricharan R wrote:
>> Introduce a new compatible and re-use 2_9_0 ops.
>>
>
> While adding a new SoC, please add more info about the controller. Like the
> hardware revision (internal/synopsys), max number of lanes supported, max link
> speed, is it a derivative etc...
>
ok sure, will add.
Regards,
Sricharan
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-09-04 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 4:57 [PATCH V2 0/6] Enable IPQ5018 PCI support Sricharan R
2024-08-27 4:57 ` [PATCH V2 1/6] dt-bindings: phy: qcom,uniphy-pcie: Document PCIe uniphy Sricharan R
2024-08-27 6:27 ` Krzysztof Kozlowski
2024-08-27 4:57 ` [PATCH V2 2/6] dt-bindings: PCI: qcom: Add IPQ5108 SoC Sricharan R
2024-08-30 8:35 ` Manivannan Sadhasivam
2024-08-27 4:57 ` [PATCH V2 3/6] phy: qcom: Introduce PCIe UNIPHY 28LP driver Sricharan R
2024-08-27 6:25 ` Krzysztof Kozlowski
2024-08-27 6:51 ` Sricharan Ramabadhran
2024-08-27 4:57 ` [PATCH V2 4/6] PCI: qcom: Add support for IPQ5018 Sricharan R
2024-08-30 8:38 ` Manivannan Sadhasivam
2024-09-04 17:21 ` Sricharan Ramabadhran [this message]
2024-08-27 4:57 ` [PATCH V2 5/6] arm64: dts: qcom: ipq5018: Add PCIe related nodes Sricharan R
2024-08-30 8:59 ` Manivannan Sadhasivam
2024-09-04 17:47 ` Sricharan Ramabadhran
2024-08-27 4:57 ` [PATCH V2 6/6] arm64: dts: qcom: ipq5018: Enable PCIe Sricharan R
2024-08-29 9:10 ` Dmitry Baryshkov
2024-08-30 7:54 ` Sricharan Ramabadhran
2024-08-27 6:24 ` [PATCH V2 0/6] Enable IPQ5018 PCI support Krzysztof Kozlowski
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=ea8ccb1e-2344-4c35-8a95-7b3f1fe23e08@quicinc.com \
--to=quic_srichara@quicinc.com \
--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=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=p.zabel@pengutronix.de \
--cc=quic_nsekar@quicinc.com \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--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