Linux USB
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	kernel@collabora.com,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv1 2/3] dt-bindings: usb: Add RK3588 EHCI
Date: Tue, 11 Apr 2023 08:12:46 -0500	[thread overview]
Message-ID: <168121876599.2908521.3687323183492928122.robh@kernel.org> (raw)
In-Reply-To: <20230406135552.23980-3-sebastian.reichel@collabora.com>


On Thu, 06 Apr 2023 15:55:51 +0200, Sebastian Reichel wrote:
> Add compatible for RK3588 EHCI. As far as I know it's fully
> compatible with generic-ehci.
> 
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
>  Documentation/devicetree/bindings/usb/generic-ehci.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 

Reviewed-by: Rob Herring <robh@kernel.org>


  reply	other threads:[~2023-04-11 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 13:55 [PATCHv1 0/3] generic-ohci/ehci: add RK3588 support Sebastian Reichel
2023-04-06 13:55 ` [PATCHv1 1/3] dt-bindings: usb: Add RK3588 OHCI Sebastian Reichel
2023-04-11 13:12   ` Rob Herring
2023-04-06 13:55 ` [PATCHv1 2/3] dt-bindings: usb: Add RK3588 EHCI Sebastian Reichel
2023-04-11 13:12   ` Rob Herring [this message]
2023-04-06 13:55 ` [PATCHv1 3/3] usb: host: ohci-platform: increase max clock number to 4 Sebastian Reichel
2023-04-06 14:09 ` [PATCHv1 0/3] generic-ohci/ehci: add RK3588 support Sebastian Reichel
  -- strict thread matches above, loose matches on Subject: below --
2023-04-04 14:53 Sebastian Reichel
2023-04-04 14:53 ` [PATCHv1 2/3] dt-bindings: usb: Add RK3588 EHCI Sebastian Reichel
2023-04-06  7:45   ` Krzysztof Kozlowski

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=168121876599.2908521.3687323183492928122.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=stern@rowland.harvard.edu \
    /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