Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
	Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Wesley Cheng <quic_wcheng@quicinc.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
	trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org,
	Ronak Raheja <ronak.raheja@oss.qualcomm.com>
Subject: Re: [PATCH v2 3/4] dt-bindings: usb: qcom,snps-dwc3: Add Kaanapali compatible
Date: Thu, 23 Oct 2025 17:41:04 +0200	[thread overview]
Message-ID: <5689050e-496b-4b03-a70b-5a5f5f90d165@kernel.org> (raw)
In-Reply-To: <20251021-knp-usb-v2-3-a2809fffcfab@oss.qualcomm.com>

On 22/10/2025 08:50, Jingyi Wang wrote:
> From: Ronak Raheja <ronak.raheja@oss.qualcomm.com>
> 
> Kaanapali uses a single-node USB controller architecture with the Synopsys
> DWC3 controller. Add this to the compatibles list to utilize the DWC3 QCOM
> and DWC3 core framework.
> 
> Signed-off-by: Ronak Raheja <ronak.raheja@oss.qualcomm.com>
> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
> ---
>  Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml | 3 +++


This does not belong to this patchset. That's USB subsystem, split it.
Please read the internal guidelines describing how to organize your
patchsets.

After splitting:

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof

  reply	other threads:[~2025-10-23 15:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  6:50 [PATCH v2 0/4] phy: qcom: Introduce USB support for Kaanapali Jingyi Wang
2025-10-22  6:50 ` [PATCH v2 1/4] dt-bindings: phy: qcom,sc8280xp-qmp-usb43dp-phy: Add Kaanapali QMP PHY Jingyi Wang
2025-10-23 15:38   ` Krzysztof Kozlowski
2025-10-22  6:50 ` [PATCH v2 2/4] dt-bindings: phy: qcom,m31-eusb2-phy: Document M31 eUSB2 PHY for Kaanapali Jingyi Wang
2025-10-23 15:39   ` Krzysztof Kozlowski
2026-01-06  5:09     ` Krishna Kurapati
2025-10-22  6:50 ` [PATCH v2 3/4] dt-bindings: usb: qcom,snps-dwc3: Add Kaanapali compatible Jingyi Wang
2025-10-23 15:41   ` Krzysztof Kozlowski [this message]
2025-10-22  6:50 ` [PATCH v2 4/4] arm64: defconfig: Add M31 eUSB2 PHY config Jingyi Wang
2025-10-27 22:36 ` (subset) [PATCH v2 0/4] phy: qcom: Introduce 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=5689050e-496b-4b03-a70b-5a5f5f90d165@kernel.org \
    --to=krzk@kernel.org \
    --cc=aiqun.yu@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jingyi.wang@oss.qualcomm.com \
    --cc=kishon@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=linux-usb@vger.kernel.org \
    --cc=quic_wcheng@quicinc.com \
    --cc=robh@kernel.org \
    --cc=ronak.raheja@oss.qualcomm.com \
    --cc=tingwei.zhang@oss.qualcomm.com \
    --cc=trilok.soni@oss.qualcomm.com \
    --cc=vkoul@kernel.org \
    --cc=yijie.yang@oss.qualcomm.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