From: Johan Jonker <jbx6244@gmail.com>
To: lindsey.stanpoor@gmail.com, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Cc: gregkh@linuxfoundation.org, cnemo@tutanota.com,
robh+dt@kernel.org, heiko@sntech.de, balbi@kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: rockchip: enable rk3328-rock64 usb3 nodes
Date: Mon, 31 Aug 2020 13:49:41 +0200 [thread overview]
Message-ID: <9751e24e-1fe2-33ab-4fa5-019af9ea7746@gmail.com> (raw)
In-Reply-To: <20200826171230.17041-2-lindsey.stanpoor@gmail.com>
Hi Cameron,
Increase the version number for each new patch serie.
git format-patch -v4 -4 HEAD
In a previous comment I gave a sort example.
However, this patch serie is about usb3, so only touch the things
related to usb3 and leave the &uart2 node (legacy ;) ) untouched.
Improve the way in which your patches are send.
Your previous serie was incomplete.
Submit all patches with the same news server (Gmail for example) that
can handle plain text, because else you get 2 different Message-Ids:
<20200826171230.17041-2-lindsey.stanpoor@gmail.com>
<20200826170623.15469-2-travelvia@airmail.cc>
git send-email --suppress-cc all --annotate --to <..> --cc <..> <patch1
patch2>
Not sure how robh filters patches, but your serie 'must' show up in the
link below or else wait for an eternity to get a ack-by.
https://patchwork.ozlabs.org/project/devicetree-bindings/list/
On 8/26/20 7:12 PM, lindsey.stanpoor@gmail.com wrote:
> From: Cameron Nemo <cnemo@tutanota.com>
>
> Enable USB3 nodes for the rk3328-based PINE Rock64 board.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> Signed-off-by: Cameron Nemo <cnemo@tutanota.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
> index 86cfb5c50a94..82c27eab6a52 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
> @@ -363,10 +363,6 @@ &tsadc {
> status = "okay";
> };
>
> -&uart2 {
> - status = "okay";
> -};
> -
> &u2phy {
> status = "okay";
>
> @@ -379,11 +375,24 @@ u2phy_otg: otg-port {
> };
> };
>
> +&uart2 {
> + status = "okay";
> +};
> +
Don't touch/change.
> &usb20_otg {
> dr_mode = "host";
> status = "okay";
> };
>
> +&usbdrd3 {
> + status = "okay";
> +};
> +
> +&usbdrd_dwc3 {
> + dr_mode = "host";
> + status = "okay";
> +};
> +
> &usb_host0_ehci {
> status = "okay";
> };
>
prev parent reply other threads:[~2020-08-31 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200826170623.15469-1-travelvia@airmail.cc>
2020-08-26 17:12 ` [PATCH 3/4] arm64: dts: rockchip: rk3328 usb3 controller node lindsey.stanpoor
2020-08-26 17:12 ` [PATCH 4/4] arm64: dts: rockchip: enable rk3328-rock64 usb3 nodes lindsey.stanpoor
2020-08-31 11:49 ` Johan Jonker [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=9751e24e-1fe2-33ab-4fa5-019af9ea7746@gmail.com \
--to=jbx6244@gmail.com \
--cc=balbi@kernel.org \
--cc=cnemo@tutanota.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=lindsey.stanpoor@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).