From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1757537AbdDRTcA (ORCPT <rfc822;w@1wt.eu>);
        Tue, 18 Apr 2017 15:32:00 -0400
Received: from foss.arm.com ([217.140.101.70]:60548 "EHLO foss.arm.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1757317AbdDRTb5 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 18 Apr 2017 15:31:57 -0400
Date: Tue, 18 Apr 2017 20:31:49 +0100
From: Marc Zyngier <marc.zyngier@arm.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: heiko@sntech.de, Mark Rutland <mark.rutland@arm.com>,
        devicetree@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>,
        Brian Norris <briannorris@chromium.org>,
        Will Deacon <will.deacon@arm.com>, linux-kernel@vger.kernel.org,
        linux-rockchip@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
        linux-arm-kernel@lists.infradead.org,
        Matthias Brugger <matthias.bgg@gmail.com>,
        Andy Yan <andy.yan@rock-chips.com>, Jianqun Xu <jay.xu@rock-chips.com>,
        Liang Chen <cl@rock-chips.com>
Subject: Re: [PATCH v3] arm64: dts: rk3399: add support for firefly-rk3399
 board
Message-ID: <20170418203149.1c68ed88@why.wild-wind.fr.eu.org>
In-Reply-To: <1491796213-4115-1-git-send-email-kever.yang@rock-chips.com>
References: <1491796213-4115-1-git-send-email-kever.yang@rock-chips.com>
Organization: ARM Ltd
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 10 Apr 2017 11:50:13 +0800
Kever Yang <kever.yang@rock-chips.com> wrote:

> Firefly-rk3399 is a bord from T-Firefly, you can find detail about
> it here:
> http://en.t-firefly.com/en/firenow/Firefly_RK3399/
> 
> This patch add basic node for the board and make it able to bring
> up.
> 
> Peripheral works:
> - usb hub which connect to ehci controller;
> - UART2 debug
> - eMMC
> - PCIe
> 
> Not work:
> - USB 3.0 HOST, type-C port
> - sdio, sd-card
> 
> Not test for other peripheral:

[...]

> - Ethernet

[...]

FWIW, I've tested the Ethernet port, which seems to work nicely.

Thanks,

	M.
-- 
Without deviation from the norm, progress is not possible.