From mboxrd@z Thu Jan  1 00:00:00 1970
From: "jay.xu" <jay.xu@rock-chips.com>
Subject: Re: [PATCH RESEND v2 4/4] ARM64: dts: rockchip: add dts file for
 RK3399 evaluation board
Date: Tue, 26 Apr 2016 09:27:16 +0800
Message-ID: <571EC3F4.2070703@rock-chips.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8;
	format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <CAD=FV=UQxoGYsrw8C2VT_-oYs3ZuJQ6eM1HAFemoGrcDJoOHfw@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
To: Doug Anderson <dianders@chromium.org>, =?UTF-8?Q?Heiko_St=c3=bcbner?= <heiko@sntech.de>
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>
List-Id: devicetree@vger.kernel.org

Hi Doug:

On 2016=E5=B9=B404=E6=9C=8826=E6=97=A5 06:23, Doug Anderson wrote:
> Hi,
>
> On Mon, Apr 25, 2016 at 12:37 AM, Heiko St=C3=BCbner <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-rev=
0"
>>
>> Yep, that should be no problem ... i.e. we also have this longer lis=
t of board
>> matches for the previous veyron boards (both in the dts files as wel=
l 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=20
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
>
>
>