mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Add Linux dts files and use them
Date: Mon, 5 May 2014 19:48:16 +0200	[thread overview]
Message-ID: <20140505174816.GY5858@pengutronix.de> (raw)
In-Reply-To: <1399305468.375736044@f93.i.mail.ru>

On Mon, May 05, 2014 at 07:57:48PM +0400, Alexander Shiyan wrote:
> Mon, 5 May 2014 10:20:49 +0200 от Sascha Hauer <s.hauer@pengutronix.de>:
> > Some updates how I intend to handle upstream dts changes in barebox.
> > 
> > - I will merge the latest upstream dts changes to barebox for each Linux
> >   rc. Should dts changes introduce regressions this will at least give us
> >   the Linux rc which introduced it
> > - I will always merge dts updates to barebox next, not to master. While
> >   dts changes may be needed in master to fix regressions on one board,
> >   they could also introduce new regressions on other boards. Should we
> >   need dts changes to fix regressions in barebox master, we have to do
> >   it using overlays in arch/*/dts/ until an upstream fix arrives in dts/
> > - I will not send the dts updates to the list, I'll just merge them to
> >   barebox next some time after a new Linux rc arrived (As just happened
> >   with 3.15-rc3)
> 
> Just to understand our further concept:
> 
> (I will use the example based on i.MX25).
> We have 3 files in the arch/arm/dts/imx25*.
> Should we now remove all of them, create our overlay for karo-tx25 board
> and include basic file <arm/imx25-karo-tx25.dts> in the top of new overlay
> file as basic DTS?

Yes, I think that's the way to go.

In the simplest case we have a arch/arm/dts/imx25-karo-tx25.dts with only a
single line:

#include <arm/imx25-karo-tx25.dts>

Then everything will be used from the upstream dts files. Additional
barebox specific stuff can be added to that file, like the environment
description.
With i.MX25 it happened that we also need SoC specific updates like for
example the iram which is not mainline. So we need a second line in
arch/arm/dts/imx25-karo-tx25.dts:

#include "imx25.dtsi"

The goal should be to mainline the SoC specific stuff so that imx25.dtsi
can be dropped, but I think we need the possibility to have SoC specific
barebox changes.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-05-05 17:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  7:45 Sascha Hauer
2014-04-28  7:45 ` [PATCH 02/12] serial: ns16550: omap: set register shift from code Sascha Hauer
2014-04-28  7:45 ` [PATCH 03/12] dts: Use dt-bindings from kernel Sascha Hauer
2014-04-28 14:22   ` Antony Pavlov
2014-04-28 18:33     ` Sascha Hauer
2014-04-30  5:49   ` [PATCH] make: dts: fix out-of-tree build Silvio Fricke
2014-05-05  7:38     ` Sascha Hauer
2014-04-28  7:45 ` [PATCH 04/12] dts: i.MX51 efika sb: Roll back pingroup changes Sascha Hauer
2014-04-28  7:45 ` [PATCH 05/12] ARM: dts: i.MX51: Use upstream dts files Sascha Hauer
2014-04-28  7:45 ` [PATCH 06/12] ARM: i.MX6: Use upstream dtsi files Sascha Hauer
2014-04-28  7:45 ` [PATCH 07/12] ARM: i.MX53: " Sascha Hauer
2014-04-28  7:45 ` [PATCH 08/12] ARM: i.MX25: Use upstream dtsi file Sascha Hauer
2014-04-28  7:45 ` [PATCH 09/12] ARM: i.MX27: " Sascha Hauer
2014-04-28  7:45 ` [PATCH 10/12] ARM: AM33xx: " Sascha Hauer
2014-04-28  7:46 ` [PATCH 11/12] ARM: Tegra20: Use upstream dtsi files Sascha Hauer
2014-04-28  7:46 ` [PATCH 12/12] ARM: dove: Use upstream dtsi file Sascha Hauer
2014-04-28 17:36   ` [PATCH] fixup! " Sebastian Hesselbarth
2014-04-28 18:40     ` Sascha Hauer
2014-05-05  8:20 ` [PATCH] Add Linux dts files and use them Sascha Hauer
2014-05-05 15:57   ` Alexander Shiyan
2014-05-05 17:48     ` Sascha Hauer [this message]
2014-05-05 18:01       ` Alexander Shiyan
2014-05-08  7:39         ` Sascha Hauer

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=20140505174816.GY5858@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=shc_work@mail.ru \
    /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