From: Wenyou.Yang at microchip.com <Wenyou.Yang@microchip.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1] ARM: dts: Makefile: Use board to decide to compile dts
Date: Fri, 23 Sep 2016 06:01:15 +0000 [thread overview]
Message-ID: <F9F4555C4E01D7469D37975B62D0EFBB3E04AB@CHN-SV-EXMX07.mchp-main.com> (raw)
In-Reply-To: <CAPnjgZ2wn1RzihXeUkmhpMyitz69yQs5vvk-7M+YtfpuMyK-8Q@mail.gmail.com>
> -----Original Message-----
> From: sjg at google.com [mailto:sjg at google.com] On Behalf Of Simon Glass
> Sent: 2016?9?23? 12:17
> To: Wenyou Yang - A41535 <Wenyou.Yang@microchip.com>
> Cc: U-Boot Mailing List <u-boot@lists.denx.de>; Stephen Warren
> <swarren@nvidia.com>; Andreas Bie?mann <andreas@biessmann.org>; Wenyou
> Yang - A41535 <Wenyou.Yang@microchip.com>
> Subject: Re: [PATCH v1] ARM: dts: Makefile: Use board to decide to compile dts
>
> Hi,
>
> On 18 September 2016 at 01:40, Wenyou Yang <wenyou.yang@atmel.com> wrote:
> > To avoid to compile all AT91 SoCs' board dts files, use the board to
> > decide to build its corresponding dts, instead of CONFIG_AT91FAMILY.
> >
> > Signed-off-by: Wenyou Yang <wenyou.yang@atmel.com>
> > ---
> >
> > arch/arm/dts/Makefile | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
>
> What is the purpose of this? It seems unnecessary to me. Compiling a few
> more .dts files will be quick.
Why we need to compile all AT91FAMILY dts files, not be used for a specific AT91 board?
It is enough to compile the dts file used for the target board. Others is unnecessary.
>
> >
> > diff --git a/arch/arm/dts/Makefile b/arch/arm/dts/Makefile index
> > 223124e..2ac1f20 100644
> > --- a/arch/arm/dts/Makefile
> > +++ b/arch/arm/dts/Makefile
> > @@ -2,10 +2,10 @@
> > # SPDX-License-Identifier: GPL-2.0+
> > #
> >
> > -dtb-$(CONFIG_AT91FAMILY) += at91sam9260-smartweb.dtb \
> > - at91sam9g20-taurus.dtb \
> > - at91sam9g45-corvus.dtb \
> > - at91sam9g45-gurnard.dtb
> > +dtb-$(CONFIG_TARGET_SMARTWEB) += at91sam9260-smartweb.dtb
> > +dtb-$(CONFIG_TARGET_TAURUS) += at91sam9g20-taurus.dtb
> > +dtb-$(CONFIG_TARGET_CORVUS) += at91sam9g45-corvus.dtb
> > +dtb-$(CONFIG_TARGET_GURNARD) += at91sam9g45-gurnard.dtb
> >
> > dtb-$(CONFIG_S5PC100) += s5pc1xx-smdkc100.dtb
> > dtb-$(CONFIG_S5PC110) += s5pc1xx-goni.dtb
> > --
> > 2.7.4
> >
>
> Regards,
> Simon
Best Regards,
Wenyou Yang
prev parent reply other threads:[~2016-09-23 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 7:40 [U-Boot] [PATCH v1] ARM: dts: Makefile: Use board to decide to compile dts Wenyou Yang
2016-09-19 13:38 ` Heiko Schocher
2016-09-23 4:16 ` Simon Glass
2016-09-23 6:01 ` Wenyou.Yang at microchip.com [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=F9F4555C4E01D7469D37975B62D0EFBB3E04AB@CHN-SV-EXMX07.mchp-main.com \
--to=wenyou.yang@microchip.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.