Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Mitchell <troy.mitchell@linux.spacemit.com>
To: Ze Huang <huang.ze@linux.dev>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Yixun Lan <dlan@gentoo.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Troy Mitchell <troy.mitchell@linux.spacemit.com>
Subject: Re: [PATCH v8 0/2] Add SpacemiT K1 USB3.0 host controller support
Date: Mon, 13 Oct 2025 17:38:05 +0800	[thread overview]
Message-ID: <AB4F40590DDC4024+aOzIfRgZZpZc3HeH@kernel.org> (raw)
In-Reply-To: <20250913-dwc3_generic-v8-0-b50f81f05f95@linux.dev>

On Sat, Sep 13, 2025 at 12:53:46AM +0800, Ze Huang wrote:
> The USB 3.0 controller found in the SpacemiT K1 SoC[1] supports both USB3.0
> Host and USB2.0 Dual-Role Device (DRD). 
> 
> This controller is compatible with DesignWare Core USB 3 (DWC3) driver.
> However, constraints in the `snps,dwc3` bindings limit the ability to describe
> hardware-specific features in a clean and maintainable way. While
> `dwc3-of-simple` still serves as a glue layer for many platforms, it requires a
> split device tree node structure, which is less desirable in newer platforms.
> 
> To promote a transition toward a flattened `dwc` node structure, this series
> introduces `dwc3-generic-plat`, building upon prior efforts that exposed the
> DWC3 core driver [2].
> 
> The device tree support for SpacemiT K1 will be submitted separately when the
> associated PHY driver is ready.
> 
> This series is based on 6.17-rc1 and has been tested on BananaPi development
> boards.
> 
> Link: https://developer.spacemit.com/documentation?token=AjHDwrW78igAAEkiHracBI9HnTb [1]
> Link: https://lore.kernel.org/all/20250414-dwc3-refactor-v7-3-f015b358722d@oss.qualcomm.com [2]
> 
> Signed-off-by: Ze Huang <huang.ze@linux.dev>
> ---
Tested-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>

Thanks,
Troy

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2025-10-13  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 16:53 [PATCH v8 0/2] Add SpacemiT K1 USB3.0 host controller support Ze Huang
2025-09-12 16:53 ` [PATCH v8 1/2] dt-bindings: usb: dwc3: add support for SpacemiT K1 Ze Huang
2025-09-12 16:53 ` [PATCH v8 2/2] usb: dwc3: add generic driver to support flattened Ze Huang
2025-10-13  9:38 ` Troy Mitchell [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=AB4F40590DDC4024+aOzIfRgZZpZc3HeH@kernel.org \
    --to=troy.mitchell@linux.spacemit.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@gentoo.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=huang.ze@linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    /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