public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>, Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	linux-rockchip@lists.infradead.org,
	linux-phy@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Frank Wang <frank.wang@rock-chips.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com
Subject: Re: [PATCH v1 02/10] dt-bindings: soc: rockchip: add rk3588 USB3 syscon
Date: Sun, 11 Feb 2024 17:37:39 +0000	[thread overview]
Message-ID: <20240211-blubber-ferocity-76ff9fdec828@spud> (raw)
In-Reply-To: <20240209181831.104687-3-sebastian.reichel@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 279 bytes --]

On Fri, Feb 09, 2024 at 07:17:18PM +0100, Sebastian Reichel wrote:
> RK3588 USB3 support requires the GRF for USB and USBDP PHY.
> 
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

Acked-by: Conor Dooley <conor.dooley@microchip.com>

Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-02-11 17:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 18:17 [PATCH v1 00/10] RK3588 USBDP support Sebastian Reichel
2024-02-09 18:17 ` [PATCH v1 01/10] dt-bindings: soc: rockchip: add clock to RK3588 VO grf Sebastian Reichel
2024-02-11 17:27   ` Conor Dooley
2024-02-09 18:17 ` [PATCH v1 02/10] dt-bindings: soc: rockchip: add rk3588 USB3 syscon Sebastian Reichel
2024-02-11 17:37   ` Conor Dooley [this message]
2024-02-09 18:17 ` [PATCH v1 03/10] dt-bindings: phy: add rockchip usbdp combo phy document Sebastian Reichel
2024-02-09 22:17   ` Heiko Stübner
2024-02-11 17:36     ` Conor Dooley
2024-02-09 18:17 ` [PATCH v1 04/10] phy: rockchip: add usbdp combo phy driver Sebastian Reichel
2024-02-11 20:45   ` Johan Jonker
2024-02-09 18:17 ` [PATCH v1 05/10] arm64: defconfig: enable Rockchip Samsung USBDP PHY Sebastian Reichel
2024-02-09 18:17 ` [PATCH v1 06/10] arm64: dts: rockchip: add USBDP phys on rk3588 Sebastian Reichel
2024-02-11 19:24   ` Johan Jonker
2024-02-12 18:48     ` Sebastian Reichel
2024-02-12 22:44       ` Johan Jonker
2024-02-09 18:17 ` [PATCH v1 07/10] arm64: dts: rockchip: add USB3 DRD controllers " Sebastian Reichel
2024-02-09 18:17 ` [PATCH v1 08/10] arm64: dts: rockchip: add USB3 to rk3588-evb1 Sebastian Reichel
2024-02-09 18:17 ` [PATCH v1 09/10] arm64: dts: rockchip: add upper USB3 port to rock-5a Sebastian Reichel
2024-02-09 18:17 ` [PATCH v1 10/10] arm64: dts: rockchip: add lower USB3 port to rock-5b Sebastian Reichel

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=20240211-blubber-ferocity-76ff9fdec828@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frank.wang@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=kever.yang@rock-chips.com \
    --cc=kishon@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --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