linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the arm-soc tree with the i2c-embedded tree
Date: Wed, 18 Jul 2012 11:29:26 +0100	[thread overview]
Message-ID: <50069006.8050301@linaro.org> (raw)
In-Reply-To: <20120718095937.GB22739@opensource.wolfsonmicro.com>

On 18/07/12 10:59, Mark Brown wrote:
> On Wed, Jul 18, 2012 at 01:33:42PM +0800, Shawn Guo wrote:
>
>> I have an IP block getting different FIFO size on different IMX SoCs.
>> We could introduce a new compatible string for driver to figure it out,
>> but I think the simpler way is just have the data encoded in device
>> tree.  In any case DT is not completely limited in encoding board
>> specific data.  Today, we have IO region and interrupt number of
>> hardware blocks encoded in DT, and to me, FIFO size could just be
>> another aspect of hardware block we could choose to encode in DT.
>
> So, this is part of the problem with encoding the description of the SoC
> into the DT - we're not doing a good job of splitting out the silicon
> description from the board specific description which is not a triumph
> for maintainability since it means that we end up needing to modify the
> DT for every board using the silicon if we want to use the new feature
> (assuming people maintain binary compatibility with old DTs, which we
> don't do a good job at either even for established DT architectures).
>
> It's not the using device tree bit that creates concern for me here,
> it's the fact that the board and silicon aren't being separated.

What's the difference?

The Device Tree describes the hardware (hardware == silicon + 
peripherals). So different platforms are different pieces of hardware. 
Everything the driver can't figure itself out from the silicon itself 
needs to be described in the DT.

We can describe the relationship with a hierarchical layout of the dts 
and dtsi files. So for my recent venture we have:

> +- db8500.dtsi       // silicon
> \	
>  +-- snowball.dts    // board

We also have plans to split it up further:

>           db8xx0.dtsi               // shared silicon
>       _________/\_________
>      /                    \
> db8500.dtsi          db8540.dtsi    // differing silicon
> \                    \
>  +-- snowball.dts     +-- new_board.dts // board

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
M: +44 77 88 633 515
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2012-07-18 10:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10  6:41 linux-next: manual merge of the arm-soc tree with the i2c-embedded tree Stephen Rothwell
2012-07-10  6:50 ` Stephen Rothwell
2012-07-10  8:38 ` Wolfram Sang
2012-07-12 13:12 ` Wolfram Sang
2012-07-12 15:54   ` Arnd Bergmann
2012-07-13 11:03     ` Lee Jones
2012-07-14 21:34   ` Linus Walleij
2012-07-16 10:17     ` Wolfram Sang
2012-07-16 11:31       ` Lee Jones
2012-07-16 13:00         ` Wolfram Sang
2012-07-16 13:55           ` Lee Jones
2012-07-17 13:06         ` Mark Brown
2012-07-17 13:30           ` Lee Jones
2012-07-17 13:35             ` Mark Brown
2012-07-17 14:02               ` Lee Jones
2012-07-17 14:22                 ` Mark Brown
2012-07-17 14:52                   ` Lee Jones
2012-07-17 15:20                     ` Mark Brown
2012-07-18  5:33                       ` Shawn Guo
2012-07-18  9:59                         ` Mark Brown
2012-07-18 10:29                           ` Lee Jones [this message]
2012-07-18 10:33                             ` Mark Brown
2012-07-18 10:43                               ` Lee Jones
2012-07-18  7:35                       ` Lee Jones
2012-07-18 11:12                         ` Mark Brown
2012-07-18 11:24                           ` Lee Jones
2012-07-16 11:37       ` Linus Walleij
2012-07-16 12:35         ` Wolfram Sang
2012-07-16 19:45           ` Linus Walleij
2012-07-16 20:04             ` Chris Ball
2012-07-17 13:10           ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2012-07-19  5:28 Stephen Rothwell
2012-09-13  6:41 Stephen Rothwell
2012-09-13  7:09 ` Uwe Kleine-König
2012-11-15  5:27 Stephen Rothwell

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=50069006.8050301@linaro.org \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).