From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sudarshan Shetty <tessolveupstream@gmail.com>,
andersson@kernel.org, konradybcio@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v12 2/3] arm64: dts: qcom: talos/qcs615-ride: Fix inconsistent USB PHY node naming
Date: Wed, 14 Jan 2026 11:19:45 +0100 [thread overview]
Message-ID: <444b2e30-5675-4a17-89dc-ca24ca3910d9@oss.qualcomm.com> (raw)
In-Reply-To: <20260114100043.1310164-3-tessolveupstream@gmail.com>
On 1/14/26 11:00 AM, Sudarshan Shetty wrote:
> The USB PHY nodes has inconsistent labels as 'usb_1_hspy'
> and 'usb_hsphy_2' across talos.dtsi and qcs615-ride.dts.
> This patch renames them to follow a consistent naming
> scheme.
Sorry for only noticing this now, but usb_hsphy_x is wrong..
*every* other dtsi uses usb_x_hsphy, please flip it around
$ rg 'usb_1_hsphy' arch -l | wc -l
93
$ rg 'usb_hsphy_1' arch -l | wc -l
0
Konrad
next prev parent reply other threads:[~2026-01-14 10:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 10:00 [PATCH v12 0/3] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Sudarshan Shetty
2026-01-14 10:00 ` [PATCH v12 1/3] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2026-01-14 10:00 ` [PATCH v12 2/3] arm64: dts: qcom: talos/qcs615-ride: Fix inconsistent USB PHY node naming Sudarshan Shetty
2026-01-14 10:19 ` Konrad Dybcio [this message]
2026-01-15 6:00 ` tessolveupstream
2026-01-16 10:06 ` Konrad Dybcio
2026-01-14 10:00 ` [PATCH v12 3/3] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board Sudarshan Shetty
2026-01-15 2:24 ` Jie Gan
2026-01-16 5:55 ` tessolveupstream
2026-01-16 7:54 ` Dmitry Baryshkov
2026-01-29 9:11 ` tessolveupstream
2026-02-04 2:58 ` Dmitry Baryshkov
2026-02-11 4:39 ` tessolveupstream
2026-01-15 8:23 ` yuanjiey
2026-01-28 11:59 ` Konrad Dybcio
2026-02-09 11:26 ` tessolveupstream
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=444b2e30-5675-4a17-89dc-ca24ca3910d9@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tessolveupstream@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox