From: djw@t-chip.com.cn
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: djw@t-chip.com.cn, linux-rockchip@lists.infradead.org,
Wayne Chou <zxf@t-chip.com.cn>, Heiko Stuebner <heiko@sntech.de>,
Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh+dt@kernel.org>,
Shawn Lin <shawn.lin@rock-chips.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Pierre-Hugues Husson <phh@phh.me>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Jacob Chen <jacob-chen@iotwrt.com>,
Brian Norris <briannorris@chromium.org>,
Will Deacon <will.deacon@arm.com>,
devicetree@vger.kernel.org,
Jagan Teki <jagan@amarulasolutions.com>,
linux-arm-kernel@lists.infradead.org,
Jianqun Xu <jay.xu@rock-chips.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Klaus Goger <klaus.goger@theobroma-systems.com>,
linux-kernel@vger.kernel.org,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v1] arm64: dts: rockchip: add support for ROC-RK3399-PC board
Date: Fri, 27 Jul 2018 15:10:32 +0800 [thread overview]
Message-ID: <871sbpm9w7.fsf@archiso.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <cd4706970b40b49373ad169e3f9651f29508194a.camel@collabora.com> (Ezequiel Garcia's message of "Thu, 26 Jul 2018 10:41:58 -0300")
Ezequiel Garcia <ezequiel@collabora.com> writes:
> On Thu, 2018-07-26 at 15:13 +0800, djw@t-chip.com.cn wrote:
>> From: Levin Du <djw@t-chip.com.cn>
>>
>> ROC-RK3399-PC is a power efficient 4GB LPDDR4 single board
>> computer with USB 3.0 and Gigabit Ethernet in a form factor
>> compatible with the Raspberry Pi. It is based on the Rockchip
>> RK3399 SoC, powered by the Type-C port.
>>
>> The devicetree currently supports peripherals of:
>>
>> - Ethernet
>> - HDMI
>> - SD Card
>> - UART2 debug
>> - TYPE-C
>
> Hi Levin,
>
> Last time I tried to make the mainline fusb driver work, it really didn't.
> Is USB 3.0 Type-C actually working with mainline on this board?
>
> Thanks!
> Eze
That's what I added in the end:
USB3 in type-c port currently only works with normal orientation,
not flip one.
Adding 'extcon=<&fusb0>' to make the dwc3 core failed to initialize.
Regards,
Levin
prev parent reply other threads:[~2018-07-27 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 7:13 [PATCH v1] arm64: dts: rockchip: add support for ROC-RK3399-PC board djw
2018-07-26 9:51 ` Enric Balletbo i Serra
2018-07-26 13:41 ` Ezequiel Garcia
2018-07-27 7:10 ` djw [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=871sbpm9w7.fsf@archiso.i-did-not-set--mail-host-address--so-tickle-me \
--to=djw@t-chip.com.cn \
--cc=arnd@arndb.de \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=jacob-chen@iotwrt.com \
--cc=jagan@amarulasolutions.com \
--cc=jay.xu@rock-chips.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=mark.rutland@arm.com \
--cc=phh@phh.me \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=xypron.glpk@gmx.de \
--cc=yamada.masahiro@socionext.com \
--cc=zxf@t-chip.com.cn \
/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).