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, Andre Przywara <andre.przywara@arm.com>,
Rob Herring <robh+dt@kernel.org>, Icenowy Zheng <icenowy@aosc.io>,
Shawn Lin <shawn.lin@rock-chips.com>,
Rask Ingemann Lambertsen <rask@formelder.dk>,
Catalin Marinas <catalin.marinas@arm.com>,
Pierre-Hugues Husson <phh@phh.me>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
Jacob Chen <jacob-chen@iotwrt.com>,
Kever Yang <kever.yang@rock-chips.com>,
linux-rockchip@lists.infradead.org,
Will Deacon <will.deacon@arm.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Jianqun Xu <jay.xu@rock-chips.com>,
Klaus Goger <klaus.goger@theobroma-systems.com>,
linux-kernel@vger.kernel.org, Heinrich Schuchardt <xypron.glpk@g>
Subject: [PATCH 0/6] phy: rockchip-typec: fix boards that does not report cable-state.
Date: Thu, 1 Mar 2018 10:24:14 +0100 [thread overview]
Message-ID: <20180301092420.1191-1-enric.balletbo@collabora.com> (raw)
Hi,
Commit c301b327aea898af ("arm64: dts: rockchip: add usb3-phy otg-port
support for rk3399") introduced a regression on some rk3399 boards,
and break USB. While some boards have support to report cable-state via
extcon interface, other boards does not support. This patch series
tries to fix this.
First and second patch makes extcon optional, the following patches
enables the typec phyter for others rk3399 boards. It has been tested on
Samsung Chromebook Plus and Sapphire but not on the other boards, so I'll
appreciate if someone can test it.
Best regards,
Enric
Enric Balletbo i Serra (6):
phy: rockchip-typec: fall back to working in host-mode if extcon is
missing.
dt-bindings: phy-rockchip-typec: move extcon property to be optional.
arm64: dts: rockchip: enable typec-phy for rk3399-sapphire.
arm64: dts: rockchip: enable typec-phy for rk3399-firefly.
arm64: dts: rockchip: enable typec-phy1 for rk3399-puma.
arm64: dts: rockchip: enable typec-phy0 for rk3399-puma-haikou.
Documentation/devicetree/bindings/phy/phy-rockchip-typec.txt | 2 ++
arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 8 ++++++++
arch/arm64/boot/dts/rockchip/rk3399-puma-haikou.dts | 4 ++++
arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 4 ++++
arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi | 8 ++++++++
drivers/phy/rockchip/phy-rockchip-typec.c | 9 ++++++---
6 files changed, 32 insertions(+), 3 deletions(-)
--
2.16.1
next reply other threads:[~2018-03-01 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 9:24 Enric Balletbo i Serra [this message]
2018-03-01 9:24 ` [PATCH 2/6] dt-bindings: phy-rockchip-typec: move extcon property to be optional Enric Balletbo i Serra
[not found] ` <20180301092420.1191-3-enric.balletbo-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
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 ` [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 ` [PATCH 6/6] arm64: dts: rockchip: enable typec-phy0 for rk3399-puma-haikou 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-1-enric.balletbo@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=clabbe.montjoie@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=heiko@sntech.de \
--cc=icenowy@aosc.io \
--cc=jacob-chen@iotwrt.com \
--cc=jay.xu@rock-chips.com \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=kishon@ti.com \
--cc=klaus.goger@theobroma-systems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=phh@phh.me \
--cc=rask@formelder.dk \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=vicencb@gmail.com \
--cc=will.deacon@arm.com \
--cc=xypron.glpk@g \
/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).