[RFC PATCH 7/7] devicetree: Add fdt_populate hook to smc91x device

Signed-off-by: Grant Likely --- hw/smc91c111.c | 20 1 files changed, 20 insertions(+), 0 deletions(-) diff --git a/hw/smc91c111.c b/hw/smc91c111.c index b7398c9..300d209 100644 --- a/hw/smc91c111.c +++ b/hw/smc91c111.c @@ -721,8 +721,28 @@ static int smc91c111_init1(SysB

[RFC PATCH 6/7] devicetree: Add fdt_populate hook to pl011 device

Signed-off-by: Grant Likely --- hw/pl011.c | 29 + 1 files changed, 25 insertions(+), 4 deletions(-) diff --git a/hw/pl011.c b/hw/pl011.c index 81de91e..efc06d2 100644 --- a/hw/pl011.c +++ b/hw/pl011.c @@ -286,6 +286,27 @@ static int pl011_load(QEMUFile *f, void *o

[RFC PATCH 5/7] devicetree: Add helper to register devices with an fdt_populate hook

This patch allows simple registration of devices to include a device tree node populate function. Signed-off-by: Grant Likely --- hw/sysbus.c | 15 +++ hw/sysbus.h |2 ++ 2 files changed, 17 insertions(+), 0 deletions(-) diff --git a/hw/sysbus.c b/hw/sysbus.c index 861572f..c

[RFC PATCH 4/7] devicetree: Add sysbus fdt populate hooks.

This patch adds sysbus specific fdt_populate hooks to fill sysbus device nodes with 'reg' and 'interrupts' properties, and to provide 'ranges' properties for correct address translations. Signed-off-by: Grant Likely --- hw/sysbus.c | 92

[RFC PATCH 3/7] devicetree: add helper for determining IRQ properties in the device tree

This patch adds the qbus_fdt_irq_to_number() helper to determine the interrupt number and phandle needed for adding the interrupts property to a device node in the device tree. Signed-off-by: Grant Likely --- hw/qdev.c | 48 hw/qdev.h |1 +

[RFC PATCH 2/7] devicetree: auto-populate the device tree with qdev data

This patch adds hooks to the qemu device model to auto-generate device tree nodes from the registered qemu devices, and calls the device tree populate hook when booting ARM platforms. Signed-off-by: Grant Likely --- hw/arm_boot.c |3 ++ hw/qdev.c | 91 +

[RFC PATCH 1/7] devicetree: Add 8k instead of double dtb size when reserving extra memory

If a small 'seed' dtb file is loaded into qemu and then heavily modified (say for runtime population of all the device nodes), then 2x the dtb size turns out not to be very much. This patch changes the device tree loading code to add a fixed 8k of additional space to the dtb buffer. Signed-off-by

[RFC PATCH 0/7] QEMU patches to generate FDT from qdevs

Hi everyone, This is an experimental set of patches for populating the flattened device tree (fdt) data from the actual set of qdevs in the platform. I'm not expecting this to get merged anytime soon, but I wanted to get it out there to solicit comments. My target for this is testing device tree

Re: [PATCH] of/address: fix dt reading on LE machines

On Mon, Apr 5, 2010 at 7:23 AM, Herring Robert-RA7055 wrote: > Grant, > >> -Original Message- >> From: glik...@secretlab.ca [mailto:glik...@secretlab.ca] On >> Behalf Of Grant Likely >> Sent: Friday, April 02, 2010 1:46 AM >> To: Herring Robert-RA7055 >> Cc: Jeremy Kerr >> Subject: Re: [PA

Re: new device tree binding review process idea

Hi Stewart, thanks for the feedback. Comments below... On Tue, Apr 6, 2010 at 9:04 AM, Yoder Stuart-B08248 wrote: > >> Device tree 'bindings' document how individual devices are described >> in the device tree.  For any given device, the binding says what >> properties and nodes a device driver

RE: devicetree platform bus bindings

Grant, > -Original Message- > From: glik...@secretlab.ca [mailto:glik...@secretlab.ca] On > Behalf Of Grant Likely > Sent: Tuesday, April 06, 2010 8:47 AM > To: Herring Robert-RA7055 > Cc: devicetree-discuss@lists.ozlabs.org > Subject: Re: devicetree platform bus bindings > > Hi Rob, >

RE: new device tree binding review process idea

> Device tree 'bindings' document how individual devices are described > in the device tree. For any given device, the binding says what > properties and nodes a device driver needs to use the device. > > This page documents the process for writing and reviewing new > bindings. New bindings are

Re: devicetree platform bus bindings

Hi Rob, On Tue, Apr 6, 2010 at 6:45 AM, Herring Robert-RA7055 wrote: > Grant, > >> > Do you plan to have generic DT parsing to platform device >> creation code or >> > will this remain platform specific? >> >> I'm actively developing this.  A while ago I decided I was not going >> to port of_plat

devicetree platform bus bindings

Grant, > > Do you plan to have generic DT parsing to platform device > creation code or > > will this remain platform specific? > > I'm actively developing this. A while ago I decided I was not going > to port of_platform_bus_type bus to any new architectures because it > is effectively just pl