From: Brian Norris <briannorris@chromium.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Caesar Wang <wxt@rock-chips.com>,
Doug Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Stephen Barber <smbarber@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Chris Zhong <zyw@rock-chips.com>
Subject: Re: [PATCH v3 2/4] arm64: dts: rockchip: add Gru/Kevin DTS
Date: Wed, 22 Mar 2017 10:57:40 -0700 [thread overview]
Message-ID: <20170322175739.GB98450@google.com> (raw)
In-Reply-To: <2390473.XAgkTqANPY@phil>
On Wed, Mar 22, 2017 at 12:59:37PM +0100, Heiko Stuebner wrote:
> Am Montag, 20. März 2017, 16:53:42 CET schrieb Brian Norris:
> > Kevin is part of a family of boards called Gru. As best as possible, the
> > properties shared by the Gru family are placed in rk3399-gru.dtsi, while
> > Kevin-specific bits are in rk3399-gru-kevin.dts. This does not add full
> > support for the base Gru board.
> >
> > Working and tested (to some extent):
> > * EC support -- including keyboard, battery, PWM, and probably more
> > * UART / console
> > * Thermal
> > * Touchscreen
> > * Touchpad
> > * Digitizer (regulator still WIP)
> > * PCIe / Wifi
> > * Bluetooth / Webcam
> > * SD card
> > * eMMC
> > * USB2 on TypeC
> > - This works much of the time, but USB3 devices may or may not detect
> > properly. Waiting on proper extcon support for USB3 over TypeC.
> > - Depends on XHCI/DWC3 fixes for ARM64 that still haven't landed
> > * Backlight
> >
> > Not working:
> > * CPUFreq -- relies on special OVP support for our PWM regulator
> > circuits
> > * EC / extcon support -- and with it, USB3/TypeC/DP
> > * DRM -- won't even build on ARM64, so all display, eDP, etc. is not
> > enabled
> >
> > Not tested:
> > * Audio
> >
> > Signed-off-by: Brian Norris <briannorris@chromium.org>
>
> applied for 4.12 with Enric's Tested-tag after some reordering of nodes/
> properties.
I realize I didn't catch 100% of the comments you wanted dropped. Thanks
for cleaning it.
Brian
next prev parent reply other threads:[~2017-03-22 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 23:53 [PATCH v3 0/4] arm64: dts: rockchip: support Google Kevin Brian Norris
2017-03-20 23:53 ` [PATCH v3 1/4] dt-bindings: Document rk3399 Gru/Kevin Brian Norris
2017-03-22 9:01 ` Heiko Stuebner
2017-03-22 17:56 ` Brian Norris
2017-03-20 23:53 ` [PATCH v3 2/4] arm64: dts: rockchip: add Gru/Kevin DTS Brian Norris
2017-03-21 11:02 ` Enric Balletbo Serra
2017-03-22 11:59 ` Heiko Stuebner
2017-03-22 17:57 ` Brian Norris [this message]
2017-03-20 23:53 ` [PATCH v3 3/4] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators Brian Norris
2017-03-21 11:04 ` Enric Balletbo Serra
2017-03-22 12:00 ` Heiko Stuebner
2017-03-20 23:53 ` [PATCH v3 4/4] arm64: dts: rockchip: add regulator info for Kevin digitizer Brian Norris
2017-03-22 8:26 ` Heiko Stuebner
2017-03-22 18:14 ` Brian Norris
2017-03-22 23:57 ` Heiko Stuebner
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=20170322175739.GB98450@google.com \
--to=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.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=robh+dt@kernel.org \
--cc=smbarber@chromium.org \
--cc=wxt@rock-chips.com \
--cc=zyw@rock-chips.com \
/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).