From: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
To: Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Subject: [PATCH v3 0/3] Add USB support for Kaanapali
Date: Mon, 6 Apr 2026 23:16:10 +0530 [thread overview]
Message-ID: <20260406174613.3388987-1-krishna.kurapati@oss.qualcomm.com> (raw)
Add support for the PHYs and controllers used for USB on Kaanapali SoCs.
V1 of this was a consolidated series of many functionlities on Kaanapali.
The first patch is patch-6 from v1 unchanges. The second and third patches
are parts of MTP and QRD specific changes (patches 14 and 16) and commit
text modified to indicate mtp and qrd specific changes are being made.
Ronak is the original author of the patches. Kept Jingyi's and mine SoB
(with no CDB) since we just rebased and send the patches in v1 and v2.
SoCCP changes [1]/[2] are needed to get ChargerFW running and receive role
notificaitons and enable vbus to test host mode. Since the SoCCP changes
are not yet acked, I enabled only device mode for now.
Changes in v3:
- Fixed repeater label in platform files
- Fixed commit text in cover letter
Link to v2:
https://lore.kernel.org/all/20260329175249.2946508-1-krishna.kurapati@oss.qualcomm.com/
Changes in v2:
- Sent USB specific changes instead of all MTP and QRD specific changes
Link to v1:
https://lore.kernel.org/all/20250924-knp-dts-v1-0-3fdbc4b9e1b1@oss.qualcomm.com/
[1]: https://lore.kernel.org/all/20260310-knp-soccp-v4-0-0a91575e0e7e@oss.qualcomm.com/
[2]: https://lore.kernel.org/all/20260326-knp-soccp-dt-v1-0-a60c2ae36e9b@oss.qualcomm.com/
Ronak Raheja (3):
arm64: dts: qcom: kaanapali: Add USB support for Kaanapali SoC
arm64: dts: qcom: kaanpaali: Add USB support for MTP platform
arm64: dts: qcom: kaanpaali: Add USB support for QRD platform
arch/arm64/boot/dts/qcom/kaanapali-mtp.dts | 27 ++++
arch/arm64/boot/dts/qcom/kaanapali-qrd.dts | 27 ++++
arch/arm64/boot/dts/qcom/kaanapali.dtsi | 154 +++++++++++++++++++++
3 files changed, 208 insertions(+)
--
2.34.1
next reply other threads:[~2026-04-06 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 17:46 Krishna Kurapati [this message]
2026-04-06 17:46 ` [PATCH v3 1/3] arm64: dts: qcom: kaanapali: Add USB support for Kaanapali SoC Krishna Kurapati
2026-04-06 19:27 ` Dmitry Baryshkov
2026-04-07 9:32 ` Konrad Dybcio
2026-04-06 17:46 ` [PATCH v3 2/3] arm64: dts: qcom: kaanpaali: Add USB support for MTP platform Krishna Kurapati
2026-04-06 19:28 ` Dmitry Baryshkov
2026-04-07 9:31 ` Konrad Dybcio
2026-04-06 17:46 ` [PATCH v3 3/3] arm64: dts: qcom: kaanpaali: Add USB support for QRD platform Krishna Kurapati
2026-04-06 19:28 ` Dmitry Baryshkov
2026-04-07 9:32 ` Konrad Dybcio
2026-05-07 20:34 ` [PATCH v3 0/3] Add USB support for Kaanapali 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=20260406174613.3388987-1-krishna.kurapati@oss.qualcomm.com \
--to=krishna.kurapati@oss.qualcomm.com \
--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=robh@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