From: travelvia@airmail.cc To: 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: [PATCH 2/4] usb: dwc3: of-simple: Add compatible for rk3328 Date: Wed, 26 Aug 2020 10:06:21 -0700 [thread overview] Message-ID: <20200826170623.15469-2-travelvia@airmail.cc> (raw) In-Reply-To: <20200826170623.15469-1-travelvia@airmail.cc> From: Cameron Nemo <cnemo@tutanota.com> 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 compatible with newer kernels. Signed-off-by: Cameron Nemo <cnemo@tutanota.com> --- drivers/usb/dwc3/dwc3-of-simple.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/dwc3/dwc3-of-simple.c b/drivers/usb/dwc3/dwc3-of-simple.c index 7df115012935..0727bf2304b1 100644 --- a/drivers/usb/dwc3/dwc3-of-simple.c +++ b/drivers/usb/dwc3/dwc3-of-simple.c @@ -171,6 +171,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 _______________________________________________ Linux-rockchip mailing list Linux-rockchip@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: travelvia@airmail.cc To: 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: [PATCH 2/4] usb: dwc3: of-simple: Add compatible for rk3328 Date: Wed, 26 Aug 2020 10:06:21 -0700 [thread overview] Message-ID: <20200826170623.15469-2-travelvia@airmail.cc> (raw) In-Reply-To: <20200826170623.15469-1-travelvia@airmail.cc> From: Cameron Nemo <cnemo@tutanota.com> 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 compatible with newer kernels. Signed-off-by: Cameron Nemo <cnemo@tutanota.com> --- drivers/usb/dwc3/dwc3-of-simple.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/dwc3/dwc3-of-simple.c b/drivers/usb/dwc3/dwc3-of-simple.c index 7df115012935..0727bf2304b1 100644 --- a/drivers/usb/dwc3/dwc3-of-simple.c +++ b/drivers/usb/dwc3/dwc3-of-simple.c @@ -171,6 +171,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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-26 17:06 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-26 17:06 [PATCH 1/4] dt-bindings: usb: add rk3328 dwc3 docs travelvia 2020-08-26 17:06 ` travelvia 2020-08-26 17:06 ` travelvia [this message] 2020-08-26 17:06 ` [PATCH 2/4] usb: dwc3: of-simple: Add compatible for rk3328 travelvia 2020-08-26 17:12 ` [PATCH 3/4] arm64: dts: rockchip: rk3328 usb3 controller node lindsey.stanpoor 2020-08-26 17:12 ` lindsey.stanpoor 2020-08-26 17:12 ` lindsey.stanpoor 2020-08-26 17:12 ` [PATCH 4/4] arm64: dts: rockchip: enable rk3328-rock64 usb3 nodes lindsey.stanpoor 2020-08-26 17:12 ` lindsey.stanpoor 2020-08-26 17:12 ` lindsey.stanpoor 2020-08-31 11:49 ` Johan Jonker 2020-08-31 11:49 ` Johan Jonker 2020-08-31 11:49 ` Johan Jonker
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=20200826170623.15469-2-travelvia@airmail.cc \ --to=travelvia@airmail.cc \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.