[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <20180515121239.18192-1-a.hajda@samsung.com>
Date: Tue, 15 May 2018 14:12:37 +0200
From: Andrzej Hajda <a.hajda@...sung.com>
To: linux-usb@...r.kernel.org (open list:DESIGNWARE USB3 DRD IP DRIVER)
Cc: Andrzej Hajda <a.hajda@...sung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
devicetree@...r.kernel.org (open list:OPEN FIRMWARE AND FLATTENED
DEVICE TREE BINDINGS), Felipe Balbi <balbi@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Inki Dae <inki.dae@...sung.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Krzysztof Kozlowski <krzk@...nel.org>,
Chanwoo Choi <cw00.choi@...sung.com>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org
Subject: [PATCH v2 0/2] USB: dwc3: get extcon device by OF graph bindings
Hi,
This small patchset tries to address issue with broken DT extcon property
in case of USB controller - DWC3. It exposes similar problem as in proposed
USB connector bindings[1] - extcon device is required by devices not always
connected directly to extcon device. Here we have:
DWC3 -> USB-PHY -> MUIC -> USB-connector
^
MHL-bridge---------------------^
More details and proposition of generic solution in first patch
v2:
- rebased on latest linux-next,
- since recently dwc3 fallbacks to ID detection using internal OTG block if
extcon property is not present, added code allowing to fallback to OTG
block also in case of graph is not present
[1]: https://marc.info/?i=20180131134435.12216-1-a.hajda%40samsung.com
Regards
Andrzej
Andrzej Hajda (2):
USB: dwc3: get extcon device by OF graph bindings
arm64: dts: exynos: add OF graph between USB-PHY and MUIC
.../dts/exynos/exynos5433-tm2-common.dtsi | 19 ++++++++++-
drivers/usb/dwc3/drd.c | 34 +++++++++++++++----
2 files changed, 46 insertions(+), 7 deletions(-)
--
2.17.0
Powered by blists - more mailing lists