From: Johan Jonker <jbx6244@gmail.com>
To: Cameron Nemo <cnemo@tutanota.com>,
Devicetree <devicetree@vger.kernel.org>,
Linux Arm Kernel <linux-arm-kernel@lists.infradead.org>,
Linux Rockchip <linux-rockchip@lists.infradead.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Cc: robh+dt@kernel.org, Heiko <heiko@sntech.de>,
balbi@kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/3] usb: dwc3: of-simple: Add compatible for rk3328
Date: Sun, 16 Aug 2020 21:23:36 +0200 [thread overview]
Message-ID: <4482f04a-d75d-6ede-acae-eb3fc7364130@gmail.com> (raw)
In-Reply-To: <MEsGWB_--3-2@tutanota.com>
Hi Cameron,
Use plain text mode for patches.
Before you introduce a new compatible string, your patch serie must
change the documents first in version 2.
See:
dwc3.txt
rockchip,dwc3.txt
(TODO but not now) Both documents are in need for a conversion to yaml.
Also sort nodes without reg alphabetically in rk3328-rock64.dts.
&u2phy {}
&uart2 {}
&usb20_otg {}
&usbdrd3 {}
&usbdrd_dwc3 {}
&usb_host0_ehci {}
&usb_host0_ohci {}
On 8/16/20 7:16 PM, Cameron Nemo wrote:
> Add a compatible to be hooked into by the Rockchip rk3328 device tree.
>
> The rk3399 compatible cannot be reused because the rk3328 SoCs may
> require a specialized driver in the future, and old device trees must
> remain commpatible with newer kernels.
>
> Signed-off-by: Cameron Nemo <cnemo@tutanota.com>
> ---
> drivers/usb/dwc3/dwc3-of-simple.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/dwc3/dwc3-of-simple.c b/drivers/usb/dwc3/dwc3-of-simple.c
> index 7df115012935..54f38e434028 100644
> --- a/drivers/usb/dwc3/dwc3-of-simple.c
> +++ b/drivers/usb/dwc3/dwc3-of-simple.c
> @@ -49,7 +49,8 @@ static int dwc3_of_simple_probe(struct platform_device *pdev)
> * Some controllers need to toggle the usb3-otg reset before trying to
> * initialize the PHY, otherwise the PHY times out.
> */
> - if (of_device_is_compatible(np, "rockchip,rk3399-dwc3"))
> + if (of_device_is_compatible(np, "rockchip,rk3399-dwc3") ||
> + of_device_is_compatible(np, "rockchip,rk3328-dwc3"))
sort alphabetically.
> simple->need_reset = true;
>
> simple->resets = of_reset_control_array_get(np, false, true,
> @@ -171,6 +172,7 @@ static const struct dev_pm_ops dwc3_of_simple_dev_pm_ops = {
> };
>
> static const struct of_device_id of_dwc3_simple_match[] = {
> + { .compatible = "rockchip,rk3328-dwc3" },
> { .compatible = "rockchip,rk3399-dwc3" },
> { .compatible = "xlnx,zynqmp-dwc3" },
> { .compatible = "cavium,octeon-7130-usb-uctl" },
> --
> 2.28.0
>
>
>
prev parent reply other threads:[~2020-08-16 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 17:16 [PATCH 1/3] usb: dwc3: of-simple: Add compatible for rk3328 Cameron Nemo
2020-08-16 17:18 ` [PATCH 2/3] arm64: dts: rockchip: rk3328 usb3 controller node Cameron Nemo
2020-08-16 17:19 ` [PATCH 3/3] arm64: dts: rockchip: enable rk3328-rock64 usb3 nodes Cameron Nemo
2020-08-16 17:27 ` Cameron Nemo
2020-08-16 19:23 ` 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=4482f04a-d75d-6ede-acae-eb3fc7364130@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=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).