LKML Archive on
help / color / mirror / Atom feed
From: Lorenzo Pieralisi <>
To: Grant Likely <>
Cc: devicetree-discuss <>,
	linaro-dev <>,
	Linux Kernel Mailing List <>
Subject: Re: Device Tree on ARM status report
Date: Tue, 08 Feb 2011 11:51:35 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, 2011-02-07 at 14:28 -0700, Grant Likely wrote:
> On Mon, Feb 7, 2011 at 1:46 AM, Amit Kucheria <> wrote:
> > On 11 Feb 05, Grant Likely wrote:
> >> 2 - Task status
> >> ---------------
> >> Core infrastructure:
> >> [glikely] basic infrastructure to enable dt: DONE
> >> [r-herring] Allow dtb to be located anywhere in RAM: DONE
> >> [bones] Debug dtb corruption during init: INPROGRESS
> >> [glikely] OF clock bindings: INPROGRESS
> >
> > Does this include the common clock framework that Jeremy had been working on?
> > I see no mention of that explicitly, hence the question.
> No, since the common clk patches are taking some time to get right,
> the device tree clock bindings have been decoupled from the common clk
> patches so that dt support doesn't get held up.  When common clk gets
> merged, the dt support will be modified to use it.

Ok Grant, good to know. I did not have time to check how the bindings
changed, but at least for vexpress I was registering and binding clocks
from DT. Here is the vexpress list of tasks updated.

Versatile express tasks:
[lorenzo-pieralisi] enable dtb support in u-boot: DONE within Linaro ?
[lorenzo-pieralisi] enable basic kernel dtb support on versatile
express: DONE
[lorenzo-pieralisi] probe clocks from dt: DONE
[lorenzo-pieralisi] probe irq controllers from device tree: DONE (basic
GIC init - interrupt routing is not there yet)
[lorenzo-pieralisi] register devices from dt: 

Currently all vexpress platform devices are registered from the DT code,
but I have to rebase to see if things changed wrt test-devicetree 

They include:

smsc911x (mdio inclusive but pending code to probe irq type)
flash physmap

The GIC and sp804 timers are also initialized from DT (they need not be
platform devices though).

Please let me know if you need further details.


  reply	other threads:[~2011-02-08 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06  4:42 Grant Likely
2011-02-06 13:36 ` Thomas Abraham
2011-02-07  8:46 ` Amit Kucheria
2011-02-07 21:28   ` Grant Likely
2011-02-08 11:51     ` Lorenzo Pieralisi [this message]
2011-02-07 11:49 ` Shawn Guo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: Device Tree on ARM status report' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).