From: Bjorn Andersson <andersson@kernel.org>
To: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Cc: Konrad Dybcio <konradybcio@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, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Add USB support for Kaanapali
Date: Mon, 30 Mar 2026 08:21:37 -0500 [thread overview]
Message-ID: <acp4bfTGOxaAQkBn@baldur> (raw)
In-Reply-To: <20260329175249.2946508-1-krishna.kurapati@oss.qualcomm.com>
On Sun, Mar 29, 2026 at 11:22:46PM +0530, Krishna Kurapati wrote:
> 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.
>
That's the correct way to do it.
> Since SoCCP changes are not acked yet, enabling only device mode.
I'm sure it clear to you what this mean, but for everyone else: what
SoCCP changes and what do you mean "acked"?
Regards,
Bjorn
>
> 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/
>
> 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
>
prev parent reply other threads:[~2026-03-30 13:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 17:52 [PATCH v2 0/3] Add USB support for Kaanapali Krishna Kurapati
2026-03-29 17:52 ` [PATCH v2 1/3] arm64: dts: qcom: kaanapali: Add USB support for Kaanapali SoC Krishna Kurapati
2026-03-30 2:52 ` Jingyi Wang
2026-03-30 9:18 ` Konrad Dybcio
2026-04-06 17:52 ` Krishna Kurapati
2026-03-29 17:52 ` [PATCH v2 2/3] arm64: dts: qcom: kaanpaali: Add USB support for MTP platform Krishna Kurapati
2026-03-30 9:19 ` Konrad Dybcio
2026-04-03 20:09 ` Akhil P Oommen
2026-04-03 20:20 ` Dmitry Baryshkov
2026-04-04 16:11 ` Akhil P Oommen
2026-04-04 19:31 ` Dmitry Baryshkov
2026-03-29 17:52 ` [PATCH v2 3/3] arm64: dts: qcom: kaanpaali: Add USB support for QRD platform Krishna Kurapati
2026-03-29 18:07 ` Dmitry Baryshkov
2026-03-29 18:15 ` Krishna Kurapati
2026-03-30 11:01 ` Dmitry Baryshkov
2026-03-30 13:21 ` Bjorn Andersson [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=acp4bfTGOxaAQkBn@baldur \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krishna.kurapati@oss.qualcomm.com \
--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