From: Vinod Koul <vkoul@kernel.org>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>
Cc: Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Prudhvi Yarlagadda <quic_pyarlaga@quicinc.com>,
Wenbin Yao <wenbin.yao@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: [PATCH v6 0/3] Add support for Glymur PCIe Gen5 x4
Date: Tue, 18 Nov 2025 22:40:59 +0530 [thread overview]
Message-ID: <aRyoo2Ve_hjgc84M@vaman> (raw)
In-Reply-To: <20251103-glymur-pcie-upstream-v6-0-18a5e0a538dc@oss.qualcomm.com>
On 03-11-25, 23:56, Qiang Yu wrote:
> Glymur is the next generation compute SoC of Qualcomm. This patch series
> aims to add support for the fourth, fifth and sixth PCIe instance on it.
> The fifth PCIe instance on Glymur has a Gen5 4-lane PHY and fourth, fifth
> and sixth PCIe instance have a Gen5 2-lane PHY.
>
> The device tree changes and whatever driver patches that are not part of
> this patch series will be posted separately after official announcement of
> the SOC.
Please rebase on phy/next, this does not apply for me
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>
Cc: Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Prudhvi Yarlagadda <quic_pyarlaga@quicinc.com>,
Wenbin Yao <wenbin.yao@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: [PATCH v6 0/3] Add support for Glymur PCIe Gen5 x4
Date: Tue, 18 Nov 2025 22:40:59 +0530 [thread overview]
Message-ID: <aRyoo2Ve_hjgc84M@vaman> (raw)
In-Reply-To: <20251103-glymur-pcie-upstream-v6-0-18a5e0a538dc@oss.qualcomm.com>
On 03-11-25, 23:56, Qiang Yu wrote:
> Glymur is the next generation compute SoC of Qualcomm. This patch series
> aims to add support for the fourth, fifth and sixth PCIe instance on it.
> The fifth PCIe instance on Glymur has a Gen5 4-lane PHY and fourth, fifth
> and sixth PCIe instance have a Gen5 2-lane PHY.
>
> The device tree changes and whatever driver patches that are not part of
> this patch series will be posted separately after official announcement of
> the SOC.
Please rebase on phy/next, this does not apply for me
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-11-18 17:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 7:56 [PATCH v6 0/3] Add support for Glymur PCIe Gen5 x4 Qiang Yu
2025-11-04 7:56 ` Qiang Yu
2025-11-04 7:56 ` [PATCH v6 1/3] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Document the Glymur QMP PCIe PHY Qiang Yu
2025-11-04 7:56 ` Qiang Yu
2025-11-04 7:56 ` [PATCH v6 2/3] phy: qcom-qmp: pcs: Add v8.50 register offsets Qiang Yu
2025-11-04 7:56 ` Qiang Yu
2025-11-04 7:56 ` [PATCH v6 3/3] phy: qcom: qmp-pcie: Add support for Glymur PCIe Gen5x4 PHY Qiang Yu
2025-11-04 7:56 ` Qiang Yu
2025-11-18 7:27 ` [PATCH v6 0/3] Add support for Glymur PCIe Gen5 x4 Qiang Yu
2025-11-18 7:27 ` Qiang Yu
2025-11-18 17:10 ` Vinod Koul [this message]
2025-11-18 17:10 ` Vinod Koul
2025-11-20 10:46 ` Qiang Yu
2025-11-20 10:46 ` Qiang Yu
2025-11-20 11:20 ` Manivannan Sadhasivam
2025-11-20 11:20 ` Manivannan Sadhasivam
2025-11-21 9:11 ` Qiang Yu
2025-11-21 9:11 ` Qiang Yu
2025-11-20 17:11 ` Vinod Koul
2025-11-20 17:11 ` Vinod Koul
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=aRyoo2Ve_hjgc84M@vaman \
--to=vkoul@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mani@kernel.org \
--cc=qiang.yu@oss.qualcomm.com \
--cc=quic_pyarlaga@quicinc.com \
--cc=robh@kernel.org \
--cc=wenbin.yao@oss.qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.