LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Grant Likely <grant.likely@secretlab.ca>,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	linaro-dev <linaro-dev@lists.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Device Tree on ARM status report
Date: Mon, 7 Feb 2011 14:28:47 -0700	[thread overview]
Message-ID: <AANLkTi=dK2qYTH7vThJb8-3wED5F_5Hcmr7nNidxs25c@mail.gmail.com> (raw)
In-Reply-To: <20110207084613.GC2723@matterhorn.lan>

On Mon, Feb 7, 2011 at 1:46 AM, Amit Kucheria <amit.kucheria@linaro.org> 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.

g.

  reply	other threads:[~2011-02-07 21:29 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 [this message]
2011-02-08 11:51     ` Lorenzo Pieralisi
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:
  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='AANLkTi=dK2qYTH7vThJb8-3wED5F_5Hcmr7nNidxs25c@mail.gmail.com' \
    --to=grant.likely@secretlab.ca \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Device Tree on ARM status report' \
    /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

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