From: Scott Wood <oss@buserror.net>
To: Rob Herring <robh+dt@kernel.org>, vabhav.sharma@nxp.com
Cc: Mark Rutland <mark.rutland@arm.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
linux-kernel-owner@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Will Deacon <will.deacon@arm.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Sriram Dash <sriram.dash@nxp.com>,
linux-clk <linux-clk@vger.kernel.org>,
Udit Kumar <udit.kumar@nxp.com>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
V.Sethi@nxp.com,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Stephen Boyd <sboyd@kernel.org>, Priyanka Jain <priyanka.jain@>
Subject: Re: [PATCH 5/5] arm64: dts: add LX2160ARDB board support
Date: Tue, 28 Aug 2018 19:28:06 -0500 [thread overview]
Message-ID: <1dd3074eabb496155c4d1abb83c82c52529a656a.camel@buserror.net> (raw)
In-Reply-To: <CAL_JsqKH4haGy2F2_2EP=evC8ip7DmGR8J4wzrO0wWnOLsaZqA@mail.gmail.com>
On Tue, 2018-08-21 at 15:45 -0500, Rob Herring wrote:
> On Mon, Aug 20, 2018 at 1:52 PM Vabhav Sharma <vabhav.sharma@nxp.com> wrote:
> > +/ {
> > + model = "NXP Layerscape LX2160ARDB";
> > + compatible = "fsl,lx2160a-rdb", "fsl,lx2160a";
> > +
> > + aliases {
> > + crypto = &crypto;
>
> Drop this. Aliases should be numbered, and this is not a standard
> alias name either.
Is this a new rule? In any case, U-Boot looks for a "crypto" alias.
-Scott
next prev parent reply other threads:[~2018-08-29 0:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 6:47 [PATCH 0/5] arm64: dts: NXP: add basic dts file for LX2160A SoC Vabhav Sharma
2018-08-20 6:47 ` [PATCH 1/5] dt-bindings: arm64: add compatible for LX2160A Vabhav Sharma
2018-08-20 6:47 ` [PATCH 2/5] soc/fsl/guts: Add compatible string " Vabhav Sharma
2018-08-20 6:47 ` [PATCH 3/5] drivers: clk-qoriq: Add clockgen support for lx2160a Vabhav Sharma
2018-08-28 22:39 ` Stephen Boyd
2018-08-29 0:18 ` Scott Wood
2018-08-30 7:36 ` Vabhav Sharma
2018-08-30 17:39 ` Scott Wood
2018-08-30 17:42 ` Scott Wood
2018-08-31 6:12 ` Andy Tang
2018-08-31 20:28 ` Scott Wood
2018-09-03 1:17 ` Andy Tang
2018-09-03 20:33 ` Scott Wood
2018-09-04 3:08 ` Andy Tang
2018-08-20 6:47 ` [PATCH 4/5] arm64: dts: add QorIQ LX2160A SoC support Vabhav Sharma
2018-08-21 10:17 ` Sudeep Holla
2018-08-23 15:00 ` Vabhav Sharma
2018-08-20 6:47 ` [PATCH 5/5] arm64: dts: add LX2160ARDB board support Vabhav Sharma
2018-08-21 20:45 ` Rob Herring
2018-08-23 15:08 ` Vabhav Sharma
2018-08-24 16:16 ` Rob Herring
2018-08-29 0:28 ` Scott Wood [this message]
2018-10-11 10:04 ` Horia Geanta
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=1dd3074eabb496155c4d1abb83c82c52529a656a.camel@buserror.net \
--to=oss@buserror.net \
--cc=V.Sethi@nxp.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sriram.dash@nxp.com \
--cc=udit.kumar@nxp.com \
--cc=vabhav.sharma@nxp.com \
--cc=viresh.kumar@linaro.org \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.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).