public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] mx6: add example DTB for mx6qsabreauto
Date: Mon, 17 Mar 2014 15:22:15 +0100	[thread overview]
Message-ID: <53270517.2010807@denx.de> (raw)
In-Reply-To: <CAOMZO5DFf8oU4Y9s89EovM2Yw4UxM2f_WQH4hMfQhGwgxH12Mg@mail.gmail.com>

Hi Fabio,

On 17/03/2014 13:54, Fabio Estevam wrote:
> Hi Stefano,
> 
> On Mon, Mar 17, 2014 at 5:58 AM, Stefano Babic <sbabic@denx.de> wrote:
> 
>> --- a/arch/arm/dts/Makefile
>> +++ b/arch/arm/dts/Makefile
>> @@ -2,6 +2,7 @@ dtb-$(CONFIG_EXYNOS5) += exynos5250-arndale.dtb \
>>         exynos5250-snow.dtb \
>>         exynos5250-smdk5250.dtb \
>>         exynos5420-smdk5420.dtb
>> +dtb-$(CONFIG_MX6) += mx6qsabreauto.dtb
> 
> It would be better to use the name as 'imx6q-sabresd.dtb' to make it
> consistent with the name we currently use in the kernel.

ok, got it.

> 
>>  dtb-$(CONFIG_TEGRA) += tegra20-harmony.dtb \
>>         tegra20-medcom-wide.dtb \
>>         tegra20-paz00.dtb \
>> diff --git a/arch/arm/dts/mx6qsabreauto.dts b/arch/arm/dts/mx6qsabreauto.dts
>> new file mode 100644
>> index 0000000..a3c9c91
>> --- /dev/null
>> +++ b/arch/arm/dts/mx6qsabreauto.dts
>> @@ -0,0 +1,13 @@
>> +/*
>> +    + * Copyright 2012 Freescale Semiconductor, Inc.
>> +    + * Copyright 2011 Linaro Ltd.
>> +    + *
>> +    + * SPDX-License-Identifier:     GPL-2.0+
>> +    + */
>> +
>> +/dts-v1/;
>> +
>> +/ {
>> +       model = "Freescale i.MX6 Quad SABRE Automotive Board";
>> +       compatible = "fsl,imx6q-sabreauto", "fsl,imx6q";
>> +};
> 
> Don't we need imx6qdl-sabresd.dtsi as well?
> 
> imx6q-sabresd.dts only contains the support that is mx6quad specific
> (sata, extra IPU, etc).
> 
> imx6qdl-sabresd.dtsi contains the common part.

Right, but it is to configure the kernel. What I am trying now is to
start adding U-Boot configuration via dtb for i.MX, not kernel
configuration, similar as we can already see for other SOC (Tegra,
zync,..). I can imagine we will have a .dtsi as well, as in kernel, but
at the moment we are starting with DT in U-Boot. Have I relly understood
your point ?

Best regards,
Stefano Babic


-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

  reply	other threads:[~2014-03-17 14:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17  8:58 [U-Boot] [PATCH 1/2] imx: add rules for U-Boot DTB support Stefano Babic
2014-03-17  8:58 ` [U-Boot] [PATCH 2/2] mx6: add example DTB for mx6qsabreauto Stefano Babic
2014-03-17 12:54   ` Fabio Estevam
2014-03-17 14:22     ` Stefano Babic [this message]
2014-03-17 14:27       ` Fabio Estevam
2014-03-17 14:40         ` Stefano Babic
2014-03-31  7:50 ` [U-Boot] [PATCH v2 1/2] imx: add rules for U-Boot DTB support Stefano Babic
2014-03-31  7:50   ` [U-Boot] [PATCH v2 2/2] mx6: add example DTB for mx6qsabreauto Stefano Babic
2014-04-09  2:19     ` Masahiro Yamada
2014-04-09  6:56       ` Stefano Babic
2014-04-02  8:47   ` [U-Boot] [PATCH v2 1/2] imx: add rules for U-Boot DTB support Stefano Babic

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=53270517.2010807@denx.de \
    --to=sbabic@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox