From: "jay.xu" <jay.xu@rock-chips.com>
To: "Doug Anderson" <dianders@chromium.org>,
"Heiko Stübner" <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>
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 [thread overview]
Message-ID: <571EC3F4.2070703@rock-chips.com> (raw)
In-Reply-To: <CAD=FV=UQxoGYsrw8C2VT_-oYs3ZuJQ6eM1HAFemoGrcDJoOHfw@mail.gmail.com>
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
>
>
>
prev parent reply other threads:[~2016-04-26 1:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 5:51 [PATCH RESEND v2 0/4] ARM64: dts: rockchip: add support for RK3399 Jianqun Xu
2016-04-22 5:51 ` [PATCH RESEND v2 1/4] Documentation: rockchip-dw-mshc: add description for rk3399 Jianqun Xu
2016-04-22 20:32 ` Rob Herring
2016-04-22 5:51 ` [PATCH RESEND v2 2/4] ARM64: dts: rockchip: add core dtsi file for RK3399 SoCs Jianqun Xu
2016-04-25 23:24 ` Brian Norris
2016-04-22 5:51 ` [PATCH RESEND v2 3/4] ARM64: dts: rockchip: add RK3399 evaluation board Jianqun Xu
2016-04-22 20:33 ` Rob Herring
2016-04-25 23:22 ` Brian Norris
2016-04-26 1:22 ` jay.xu
2016-04-26 1:30 ` jay.xu
2016-04-22 5:51 ` [PATCH RESEND v2 4/4] ARM64: dts: rockchip: add dts file for " Jianqun Xu
2016-04-25 1:47 ` Caesar Wang
2016-04-25 7:37 ` Heiko Stübner
2016-04-25 22:23 ` Doug Anderson
2016-04-26 1:27 ` jay.xu [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=571EC3F4.2070703@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=caesar.upstream@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=davidriley@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jwerner@chromium.org \
--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=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=smbarber@chromium.org \
--cc=will.deacon@arm.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