All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] fdt: Add board specific dts inclusion
Date: Mon, 9 Jul 2012 14:37:30 -0700	[thread overview]
Message-ID: <CAPnjgZ1db1a1rEGLJKXqcytoNA19m3m=uDDSpjPy1PDH3rjNug@mail.gmail.com> (raw)
In-Reply-To: <4FFA8B5A.9060806@monstr.eu>

On Mon, Jul 9, 2012 at 12:42 AM, Michal Simek <monstr@monstr.eu> wrote:

> On 07/04/2012 10:25 PM, Stephan Linz wrote:
>
>> Some architectures, for example Microblaze, doesn't need a
>> splitted device tree because every Microblaze hw design is
>> different. The individuell Microblaze device tree will be
>> auto generated by FPGA design tools and could be used directly
>> with dtc.
>>
>> The auto generated dts for Microblaze can not processed by CPP.
>> Unfortunately that is the default procedure in U-Boot to merge
>> a splitted device tree (substitution of ARCH_CPU_DTS).
>>
>> Microblaze will never use the ARCH_CPU_DTS substitution and we
>> introduce the new board specific substitution variable BOARD_DTS
>> that points into vendor/board/dts subdir with the file name
>> of CONFIG_DEFAULT_DEVICE_TREE. The common dts file in vendor/dts
>> subdir (defined by CONFIG_DEFAULT_DEVICE_TREE) contain a single
>> include line that can processed by CPP:
>>
>>      /include/ BOARD_DTS
>>
>> Signed-off-by: Stephan Linz<linz@li-pro.net>
>> ---
>>   dts/Makefile |    3 ++-
>>   1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/dts/Makefile b/dts/Makefile
>> index 914e479..b1f47a1 100644
>> --- a/dts/Makefile
>> +++ b/dts/Makefile
>> @@ -36,7 +36,8 @@ $(error Your architecture does not have device tree
>> support enabled. \
>>   Please define CONFIG_ARCH_DEVICE_TREE))
>>
>>   # We preprocess the device tree file provide a useful define
>> -DTS_CPPFLAGS := -DARCH_CPU_DTS=\"$(SRCTREE)/**arch/$(ARCH)/dts/$(CONFIG_
>> **ARCH_DEVICE_TREE).dtsi\"
>> +DTS_CPPFLAGS := -DARCH_CPU_DTS=\"$(SRCTREE)/**arch/$(ARCH)/dts/$(CONFIG_
>> **ARCH_DEVICE_TREE).dtsi\" \
>> +               -DBOARD_DTS=\"$(SRCTREE)/**board/$(VENDOR)/$(BOARD)/dts/$
>> **(DEVICE_TREE).dts\"
>>
>>   all:  $(obj).depend $(LIB)
>>
>>
> Ok. Have tested this.
> Simon can you give your ACK for this patch?
>

Weill I think for now it is reasonable.

Acked-by: Simon Glass <sjg@chromium.org>


>
> Tested-by: Michal Simek <monstr@monstr.eu>
>
> I think I can add this one to my microblaze custodian tree.
>
> Thanks,
> Michal
>
>
>
> --
> Michal Simek, Ing. (M.Eng)
> w: www.monstr.eu p: +42-0-721842854
> Maintainer of Linux kernel 2.6 Microblaze Linux -
> http://www.monstr.eu/fdt/
> Microblaze U-BOOT custodian
>

  reply	other threads:[~2012-07-09 21:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 20:25 [U-Boot] [PATCH 1/3] fdt: Add board specific dts inclusion Stephan Linz
2012-07-04 20:25 ` [U-Boot] [PATCH 2/3] microblaze: Wire up dts configuration Stephan Linz
2012-07-10  8:03   ` Michal Simek
2012-07-04 20:25 ` [U-Boot] [PATCH 3/3] microblaze: Wire up OF support for emaclite Stephan Linz
2012-07-09 21:42   ` Simon Glass
2012-07-10  8:04     ` Michal Simek
2012-07-09  7:42 ` [U-Boot] [PATCH 1/3] fdt: Add board specific dts inclusion Michal Simek
2012-07-09 21:37   ` Simon Glass [this message]
2012-07-10  8:03     ` Michal Simek

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='CAPnjgZ1db1a1rEGLJKXqcytoNA19m3m=uDDSpjPy1PDH3rjNug@mail.gmail.com' \
    --to=sjg@chromium.org \
    --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.