From: Enric Balletbo i Serra <enric.balletbo@collabora.com> To: kishon@ti.com, heiko@sntech.de Cc: groeck@chromium.org, gwendal@chromium.org, kernel@collabora.com, vicencb@gmail.com, devicetree@vger.kernel.org, Pierre-Hugues Husson <phh@phh.me>, Jianqun Xu <jay.xu@rock-chips.com>, Kever Yang <kever.yang@rock-chips.com>, linux-kernel@vger.kernel.org, Heinrich Schuchardt <xypron.glpk@gmx.de>, linux-rockchip@lists.infradead.org, Shawn Lin <shawn.lin@rock-chips.com>, Rob Herring <robh+dt@kernel.org>, Will Deacon <will.deacon@arm.com>, Mark Rutland <mark.rutland@arm.com>, Catalin Marinas <catalin.marinas@arm.com>, linux-arm-kernel@lists.infradead.org Subject: [PATCH 4/6] arm64: dts: rockchip: enable typec-phy for rk3399-firefly. Date: Thu, 1 Mar 2018 10:24:18 +0100 [thread overview] Message-ID: <20180301092420.1191-5-enric.balletbo@collabora.com> (raw) In-Reply-To: <20180301092420.1191-1-enric.balletbo@collabora.com> Commit c301b327aea898af ("arm64: dts: rockchip: add usb3-phy otg-port support for rk3399") caused a regression regarding the USB3. During boot, the following message appears a few times: dwc3: failed to initialize core The driver is deferred waiting for the typec-phy, but this never happens beause is disabled. So, enable it. Fixes: c301b327aea898af ("arm64: dts: rockchip: add usb3-phy otg-port support for rk3399") Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> --- arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts index 4f28628aa091..0e3a9ab4a297 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts +++ b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts @@ -670,6 +670,14 @@ status = "okay"; }; +&tcphy0 { + status = "okay"; +}; + +&tcphy1 { + status = "okay"; +}; + &u2phy0 { status = "okay"; -- 2.16.1
WARNING: multiple messages have this Message-ID (diff)
From: enric.balletbo@collabora.com (Enric Balletbo i Serra) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 4/6] arm64: dts: rockchip: enable typec-phy for rk3399-firefly. Date: Thu, 1 Mar 2018 10:24:18 +0100 [thread overview] Message-ID: <20180301092420.1191-5-enric.balletbo@collabora.com> (raw) In-Reply-To: <20180301092420.1191-1-enric.balletbo@collabora.com> Commit c301b327aea898af ("arm64: dts: rockchip: add usb3-phy otg-port support for rk3399") caused a regression regarding the USB3. During boot, the following message appears a few times: dwc3: failed to initialize core The driver is deferred waiting for the typec-phy, but this never happens beause is disabled. So, enable it. Fixes: c301b327aea898af ("arm64: dts: rockchip: add usb3-phy otg-port support for rk3399") Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> --- arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts index 4f28628aa091..0e3a9ab4a297 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts +++ b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts @@ -670,6 +670,14 @@ status = "okay"; }; +&tcphy0 { + status = "okay"; +}; + +&tcphy1 { + status = "okay"; +}; + &u2phy0 { status = "okay"; -- 2.16.1
next prev parent reply other threads:[~2018-03-01 9:26 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-01 9:24 [PATCH 0/6] phy: rockchip-typec: fix boards that does not report cable-state Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra 2018-03-01 9:24 ` [PATCH 1/6] phy: rockchip-typec: fall back to working in host-mode if extcon is missing Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra 2018-03-01 9:45 ` Heiko Stübner 2018-03-01 9:45 ` Heiko Stübner 2018-03-01 12:15 ` Enric Balletbo i Serra 2018-03-01 12:15 ` Enric Balletbo i Serra 2018-03-01 9:24 ` [PATCH 2/6] dt-bindings: phy-rockchip-typec: move extcon property to be optional Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra 2018-03-01 9:49 ` Heiko Stübner 2018-03-01 9:49 ` Heiko Stübner 2018-03-01 9:49 ` Heiko Stübner 2018-03-01 9:24 ` [PATCH 3/6] arm64: dts: rockchip: enable typec-phy for rk3399-sapphire Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra [this message] 2018-03-01 9:24 ` [PATCH 4/6] arm64: dts: rockchip: enable typec-phy for rk3399-firefly Enric Balletbo i Serra 2018-03-01 9:24 ` [PATCH 5/6] arm64: dts: rockchip: enable typec-phy1 for rk3399-puma Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra 2018-03-01 9:24 ` [PATCH 6/6] arm64: dts: rockchip: enable typec-phy0 for rk3399-puma-haikou Enric Balletbo i Serra 2018-03-01 9:24 ` Enric Balletbo i Serra
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=20180301092420.1191-5-enric.balletbo@collabora.com \ --to=enric.balletbo@collabora.com \ --cc=catalin.marinas@arm.com \ --cc=devicetree@vger.kernel.org \ --cc=groeck@chromium.org \ --cc=gwendal@chromium.org \ --cc=heiko@sntech.de \ --cc=jay.xu@rock-chips.com \ --cc=kernel@collabora.com \ --cc=kever.yang@rock-chips.com \ --cc=kishon@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=mark.rutland@arm.com \ --cc=phh@phh.me \ --cc=robh+dt@kernel.org \ --cc=shawn.lin@rock-chips.com \ --cc=vicencb@gmail.com \ --cc=will.deacon@arm.com \ --cc=xypron.glpk@gmx.de \ /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.