From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
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
Subject: Re: [PATCH v3 5/5] arch: arm64: dts: qcom: Add support for PCIe3a
Date: Thu, 16 Apr 2026 08:19:09 +0200 [thread overview]
Message-ID: <d486616b-ef21-4933-aaf5-dcba339dd8cc@kernel.org> (raw)
In-Reply-To: <aeBWfv1oXnSQC454@hu-qianyu-lv.qualcomm.com>
On 16/04/2026 05:24, Qiang Yu wrote:
> On Wed, Apr 15, 2026 at 09:44:15AM +0200, Krzysztof Kozlowski wrote:
>> On Sun, Apr 12, 2026 at 11:26:00PM -0700, Qiang Yu wrote:
>>> Describe PCIe3a controller and PHY. Also add required system resources
>>> like regulators, clocks, interrupts and registers configuration for PCIe3a.
>>>
>>> Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
>>
>> subject: drop arch.
>>
>> Please use subject prefixes matching the subsystem. You can get them for
>> example with 'git log --oneline -- DIRECTORY_OR_FILE' on the directory
>> your patch is touching. For bindings, the preferred subjects are
>> explained here:
>> https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
>>
>
> Thanks for pointing me the link. I’ll drop arch: in next version.
>
>>> ---
>>> arch/arm64/boot/dts/qcom/glymur.dtsi | 316 ++++++++++++++++++++++++++++++++++-
>>> 1 file changed, 315 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/glymur.dtsi b/arch/arm64/boot/dts/qcom/glymur.dtsi
>>> index f23cf81ddb77a4138deeb4e00dd8b316930a2feb..c15f87c37ecbad72076a6c731f4959a1a8bd8425 100644
>>> --- a/arch/arm64/boot/dts/qcom/glymur.dtsi
>>> +++ b/arch/arm64/boot/dts/qcom/glymur.dtsi
>>> @@ -736,7 +736,7 @@ gcc: clock-controller@100000 {
>>> <0>, /* USB 2 Phy PCIE PIPEGMUX */
>>> <0>, /* USB 2 Phy PIPEGMUX */
>>> <0>, /* USB 2 Phy SYS PCIE PIPEGMUX */
>>> - <0>, /* PCIe 3a */
>>> + <&pcie3a_phy>, /* PCIe 3a */
>>> <&pcie3b_phy>, /* PCIe 3b */
>>> <&pcie4_phy>, /* PCIe 4 */
>>> <&pcie5_phy>, /* PCIe 5 */
>>> @@ -3640,6 +3640,320 @@ pcie3b_port0: pcie@0 {
>>> };
>>
>> ...
>>
>>>> + pcie3a_phy: phy@f00000 {
>>
>> Same comment as before.
>>
>
> The existing PCIe/PHY nodes are not strictly ordered by address. Current
> order is:
Obviously we cannot even keep order of nodes when creating a new DTSI
file from scratch.
But adding @f00000 after @1c10000 makes even less sense, regardless how
bad existing code is. Don't make it worse!
This goes before phy@fa0000
>
> - pcie4: pci@1bf0000
> - pcie4_phy: phy@1bf6000
> - pcie5: pci@1b40000
> - pcie5_phy: phy@1b50000
> - pcie6: pci@1c00000
> - pcie6_phy: phy@1c06000
> - pcie3b: pci@1b80000
> - pcie3a: pci@1c10000 (added in this patch)
> - pcie3a_phy: phy@f00000 (added in this patch)
> - pcie3b_phy: phy@f10000
>
> Do you want me to reorder these nodes to follow strict address order?
No, but don't add nodes randomly or following the previous broken order.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-04-16 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 6:25 [PATCH v3 0/5] phy: qcom: qmp-pcie: Add PCIe Gen5 8-lane bifurcation support for Glymur Qiang Yu
2026-04-13 6:25 ` [PATCH v3 1/5] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Add support for glymur Gen5 x8 bifurcation mode Qiang Yu
2026-04-15 7:50 ` Krzysztof Kozlowski
2026-04-16 2:58 ` Qiang Yu
2026-04-17 9:18 ` Krzysztof Kozlowski
2026-04-13 6:25 ` [PATCH v3 2/5] phy: qcom: qmp-pcie: Add multiple power-domains support Qiang Yu
2026-04-13 6:25 ` [PATCH v3 3/5] phy: qcom: qmp-pcie: Support multiple nocsr resets Qiang Yu
2026-04-13 8:10 ` Philipp Zabel
2026-04-16 3:02 ` Qiang Yu
2026-04-13 6:25 ` [PATCH v3 4/5] phy: qcom: qmp-pcie: Add Gen5 8-lanes mode for Glymur Qiang Yu
2026-04-13 6:26 ` [PATCH v3 5/5] arch: arm64: dts: qcom: Add support for PCIe3a Qiang Yu
2026-04-15 7:44 ` Krzysztof Kozlowski
2026-04-16 3:24 ` Qiang Yu
2026-04-16 6:19 ` Krzysztof Kozlowski [this message]
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=d486616b-ef21-4933-aaf5-dcba339dd8cc@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@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=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=qiang.yu@oss.qualcomm.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