Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751840AbcDZB13 (ORCPT <rfc822;w@1wt.eu>);
	Mon, 25 Apr 2016 21:27:29 -0400
Received: from regular1.263xmail.com ([211.150.99.137]:38780 "EHLO
	regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750749AbcDZB10 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 25 Apr 2016 21:27:26 -0400
X-263anti-spam: KSV:0;
X-MAIL-GRAY: 0
X-MAIL-DELIVERY: 1
X-ABS-CHECKED: 4
X-ADDR-CHECKED: 0
X-KSVirus-check: 0
X-RL-SENDER: jay.xu@rock-chips.com
X-FST-TO: linux-rockchip@lists.infradead.org
X-SENDER-IP: 58.22.7.114
X-LOGIN-NAME: jay.xu@rock-chips.com
X-UNIQUE-TAG: <1fccc703ad14d6051d4035ec8a1488ac>
X-ATTACHMENT-NUM: 0
X-DNS-TYPE: 0
Subject: Re: [PATCH RESEND v2 4/4] ARM64: dts: rockchip: add dts file for
 RK3399 evaluation board
To: Doug Anderson <dianders@chromium.org>,
        =?UTF-8?Q?Heiko_St=c3=bcbner?= <heiko@sntech.de>
References: <1461304307-14113-1-git-send-email-jay.xu@rock-chips.com>
 <1461304307-14113-5-git-send-email-jay.xu@rock-chips.com>
 <571D7723.1020707@gmail.com> <4687144.rPskt7YEHJ@diego>
 <CAD=FV=UQxoGYsrw8C2VT_-oYs3ZuJQ6eM1HAFemoGrcDJoOHfw@mail.gmail.com>
Cc: Caesar Wang <caesar.upstream@gmail.com>, Rob Herring <robh+dt@kernel.org>,
        Pawel Moll <pawel.moll@arm.com>, Mark Rutland <mark.rutland@arm.com>,
        Ian Campbell <ijc+devicetree@hellion.org.uk>,
        Kumar Gala <galak@codeaurora.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will.deacon@arm.com>, Tao Huang <huangtao@rock-chips.com>,
        David Riley <davidriley@chromium.org>,
        Julius Werner <jwerner@chromium.org>, smbarber@chromium.org,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
        "open list:ARM/Rockchip SoC..." <linux-rockchip@lists.infradead.org>
From: "jay.xu" <jay.xu@rock-chips.com>
Message-ID: <571EC3F4.2070703@rock-chips.com>
Date: Tue, 26 Apr 2016 09:27:16 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAD=FV=UQxoGYsrw8C2VT_-oYs3ZuJQ6eM1HAFemoGrcDJoOHfw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 927
Lines: 29

Hi Doug:

On 2016年04月26日 06:23, Doug Anderson wrote:
> Hi,
>
> On Mon, Apr 25, 2016 at 12:37 AM, Heiko Stübner <heiko@sntech.de> wrote:
>>> Can we add the following strings to match the loader (coreboot)?
>>>    No matter, we can match the loader(coreboot) to bring up the evb board
>>> on now or in the future.
>>>
>>> ...,"google,rk3399evb-rev3",
>>> google,rk3399evb-rev2",google,rk3399evb-rev1","google,rk3399evb-rev0"
>>
>> Yep, that should be no problem ... i.e. we also have this longer list of board
>> matches for the previous veyron boards (both in the dts files as well as the
>> board-binding document)
>
> Just to make sure we're on the same page: I presume we're expecting
> the Jay spin with this change?
>
Got it, and do you think it's better to use rk3399-evb-rev1 but 
rk3399evb-rev1, since the dts use rk3399-evb ?

Anyway I just want to point out that we needn't to fix in the future.

> -Doug
>
>
>