From: Johan Hovold <johan+linaro@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH 0/4] arm64: dts: qcom: sc8280xp: fix USB/DP PHYs
Date: Mon, 19 Sep 2022 11:44:50 +0200 [thread overview]
Message-ID: <20220919094454.1574-1-johan+linaro@kernel.org> (raw)
When adding a check for overlapping register regions to the QMP PHY
drivers I noticed that the USB4/USB3/DP PHY nodes are currently broken
in multiple ways.
This series fixes the SS PHY nodes and drops the DP PHY nodes which can
be added back after the binding and driver has been updated.
These should ideally go into 6.0.
Johan
Johan Hovold (4):
arm64: dts: qcom: sc8280xp: fix USB0 PHY PCS_MISC registers
arm64: dts: qcom: sc8280xp: fix USB1 PHY RX1 registers
arm64: dts: qcom: sc8280xp: fix USB PHY PCS registers
arm64: dts: qcom: sc8280xp: drop broken DP PHY nodes
arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 28 ++++----------------------
1 file changed, 4 insertions(+), 24 deletions(-)
--
2.35.1
next reply other threads:[~2022-09-19 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 9:44 Johan Hovold [this message]
2022-09-19 9:44 ` [PATCH 1/4] arm64: dts: qcom: sc8280xp: fix USB0 PHY PCS_MISC registers Johan Hovold
2022-10-17 20:50 ` Andrew Halaney
2022-09-19 9:44 ` [PATCH 2/4] arm64: dts: qcom: sc8280xp: fix USB1 PHY RX1 registers Johan Hovold
2022-10-17 20:56 ` Andrew Halaney
2022-09-19 9:44 ` [PATCH 3/4] arm64: dts: qcom: sc8280xp: fix USB PHY PCS registers Johan Hovold
2022-10-17 20:59 ` Andrew Halaney
2022-09-19 9:44 ` [PATCH 4/4] arm64: dts: qcom: sc8280xp: drop broken DP PHY nodes Johan Hovold
2022-10-18 3:05 ` [PATCH 0/4] arm64: dts: qcom: sc8280xp: fix USB/DP PHYs Bjorn Andersson
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=20220919094454.1574-1-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).