Devicetree
 help / color / mirror / Atom feed
From: Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: Respinning my test-devicetree branch
Date: Sat, 24 Jul 2010 23:48:31 +0200	[thread overview]
Message-ID: <1280008111.2198.23.camel@pororo.lan> (raw)
In-Reply-To: <AANLkTimsJRHchDJPemDkz6wkXgTzYtS_c0eDru6uQXt--JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Grant,

> I've respun my test-devicetree branch and dropped a bunch of patches
> in preference for ones in your arm-dt branch.  Here are my notes as I
> was working on it.

OK, cool. The patches aren't 100% confirmed yet - Nicolas and I are
still chatting about the specifics of machine-id allocation and probing
for device tree boot. I'm proposing a single machine ID for device tee
boot, and looking up a mdesc later (probing via the device tree). His
preference is a per-SOC machine IDs (eg, "omap4 with device tree
support", and no later DT probe.

However, it won't be difficult to cater for either as we go along.

> - skipped 94b9eca arm/dt: Allow CONFIG_OF on ARM
>    The version in my tree reflects changes to the drivers/of code

OK.

> - cherry picked 5769648 arm/dt: postpone mdesc lookup until setup_arch
> when booting with a DT
>   - qemu would no longer boot on normal versatilepb with this patch.
> Had to change compare to use "beq" to get it to boot.

OK, sounds reasonable - I hadn't tested that change on non-DT. I should
figure out why testing the carry bit doesn't work, as it made sense at
the time :)

> - cherry picked 4ac36ea arm/dt: allow bootmem reservation for device tree blob
>   - Please add my s-o-b line to this patch.  A chunk of that patch
> seems to be based on one of the patches I wrote ("arm/devicetree:
> Reserve memory used by dtb blob".  Correct me if I'm not remembering
> correctly).

Yes; it's a patch with multiple contributions from both of us; I must
have dropped your signoff at some point, sorry about that.

> - cherry picked fbdf9cf arm/dt: hook device tree setup into boot code
> - cherry picked 47ae655 arm/dt: probe for platforms via the device tree
> - cherry picked f528a85 drivers/amba: separate periphid probe logic
> from amba_device_register
> - cherry picked bf5ef5c drivers/amba: probe via device tree
> 

> I cherry picked the generic clock stuff, but I should probably merge
> in your clock tree instead.  None of this is stuff that I will be
> carrying in my tree over the long term:
> - cherry picked b156e35 Add a common struct clk
> - cherry picked 0a2e3d8 clk: Generic support for fixed-rate clocks
> - cherry picked 122a467 arm/clkdev: Allow common struct clk usage
> - cherry picked 8a9c892 arm/plat-versatile: convert to common struct clk

OK. These clock changed are merged in my DT branch to make the versatile
DT port easier; but it's possible to merge that separately. I've posted
the base clk infrastructure changes to rmk's tree, I think we're making
progress to have that accepted. Once that is done, the versatile port to
the new clk code should be fairly unintrusive.

> For the of-clocks I've cherry picked the following and then made some
> changes on top:
> - cherry picked 0177ef5 of: add clock providers
>   - Fixed up Kconfig conflicts
> - cherry picked 6bdbbd7 of/clk: parse fixed clocks

This one could do with some sanity checking; the DT parsing may be a
little naïve.

> - cherry picked c0e03fa arm/clkdev: lookup clocks from OF clock providers
> - Added patch "of/clock: rework to new binding"
>   - I'm still working on this.  I'll post to the ML it I've tested it.

OK, cool.

> Finally I've cherry picked the modified versatile platform, and made a
> few changes for my own purpose.
> - cherry picked 91eb8b8 arm/versatile: add a device tree versatile platform
> - squashed into 91eb8b8:  b1e67d2 arm/versatile: probe devices from device tree
> 
> Also have a couple of patches on top to fix a phandle endian issue and
> to fix booting of versatilepb when the dt patches are applied:

All looks good, thanks for that!

Cheers,


Jeremy

_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

      parent reply	other threads:[~2010-07-24 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23  8:16 Respinning my test-devicetree branch Grant Likely
     [not found] ` <AANLkTimsJRHchDJPemDkz6wkXgTzYtS_c0eDru6uQXt--JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-24 21:48   ` Jeremy Kerr [this message]

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=1280008111.2198.23.camel@pororo.lan \
    --to=jeremy.kerr-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.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