public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Riesch <michael.riesch@wolfvision.net>
To: Samuel Holland <samuel@sholland.org>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Vinod Koul <vkoul@kernel.org>, Heiko Stuebner <heiko@sntech.de>
Cc: Peter Geis <pgwipeout@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 0/6] phy: rockchip-inno-usb2: RK356x OTG fix and enhancements
Date: Thu, 14 Apr 2022 16:00:29 +0200	[thread overview]
Message-ID: <8b67b7e8-29f2-49e0-ff99-5a13e73f4b62@wolfvision.net> (raw)
In-Reply-To: <20220414032258.40984-1-samuel@sholland.org>

Hello Samuel,

On 4/14/22 05:22, Samuel Holland wrote:
> This series gets USB OTG working on the RK356x SoCs, as used in the
> PineNote tablet.
> 
>  - Patch 1 fixes an interrupt storm issue specific to RK356x.
>  - Patches 2 and 3 are a couple of small optimizations.
>  - Patches 4 and 5 reduce the delay when unplugging from the OTG port.
>  - Patch 6 allows OTG ports to work in host mode without depending on
>    another driver to provide an extcon. The specific use case here is
>    a Type-C port controller that provides a hardware "ID pin" output.
> 
> 
> Samuel Holland (6):
>   phy: rockchip-inno-usb2: Fix muxed interrupt support
>   phy: rockchip-inno-usb2: Do not check bvalid twice
>   phy: rockchip-inno-usb2: Do not lock in bvalid IRQ handler
>   phy: rockchip-inno-usb2: Support multi-bit mask properties
>   phy: rockchip-inno-usb2: Handle bvalid falling
>   phy: rockchip-inno-usb2: Handle ID IRQ
> 
>  drivers/phy/rockchip/phy-rockchip-inno-usb2.c | 125 +++++++++++++++---
>  1 file changed, 105 insertions(+), 20 deletions(-)

Thanks a lot! This series fixes the USB gadget operation of my RK356x
boards.

With suitable DTS changes, the zero gadget module, and usbtest

Tested-by: Michael Riesch <michael.riesch@wolfvision.net>

on a RK3568 EVB1 and a Rock 3 Model A.

Best regards,
Michael

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

  parent reply	other threads:[~2022-04-14 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  3:22 [PATCH 0/6] phy: rockchip-inno-usb2: RK356x OTG fix and enhancements Samuel Holland
2022-04-14  3:22 ` [PATCH 1/6] phy: rockchip-inno-usb2: Fix muxed interrupt support Samuel Holland
2022-04-14  3:22 ` [PATCH 2/6] phy: rockchip-inno-usb2: Do not check bvalid twice Samuel Holland
2022-04-14  3:22 ` [PATCH 3/6] phy: rockchip-inno-usb2: Do not lock in bvalid IRQ handler Samuel Holland
2022-04-14  3:22 ` [PATCH 4/6] phy: rockchip-inno-usb2: Support multi-bit mask properties Samuel Holland
2022-04-14  3:22 ` [PATCH 5/6] phy: rockchip-inno-usb2: Handle bvalid falling Samuel Holland
2022-04-14  3:22 ` [PATCH 6/6] phy: rockchip-inno-usb2: Handle ID IRQ Samuel Holland
2022-04-14 14:00 ` Michael Riesch [this message]
2022-04-20  9:14 ` [PATCH 0/6] phy: rockchip-inno-usb2: RK356x OTG fix and enhancements Vinod Koul

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=8b67b7e8-29f2-49e0-ff99-5a13e73f4b62@wolfvision.net \
    --to=michael.riesch@wolfvision.net \
    --cc=heiko@sntech.de \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=pgwipeout@gmail.com \
    --cc=samuel@sholland.org \
    --cc=vkoul@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