Re: [Power.org:parch] devicetree: Musings on reserved regions

[Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>]

On Mon, 2011-02-07 at 14:45 -0700, Grant Likely wrote:
> On Mon, Feb 7, 2011 at 2:39 PM, Benjamin Herrenschmidt
> <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org> wrote:
> >
> >> In addition to the reserved regions block in the header, define a set
> >> of properties in the memory node that specify the reserved regions
> >> with the name reflecting the usage.
> >> For example:
> >>
> >>       memory@0 {
> >>               device_type = "memory";
> >>               reg = <0 0x40000000>;
> >>               reserved-ramdisk = <0xc00000 0x200000>; /* 2MB ramdisk */
> >>               reserved-dtb = <0xbf0000 0x1000>; /* devicetree */
> >>               reserved-fb0 = 0x1000000 0x400000>; /* framebuffer */
> >>       };
> >>
> >> Each reserved property would start with "reserved-" followed by a
> >> name.  reserved-ramdisk and reserved-dtb would be reserved for ramdisk
> >> and dtb images respectively.  Other names could also be defined; for
> >> example, reserved-openfirmware.
> >
> > I very much dislike the list of properties with magic names. I'd rather
> > have a pair of properties containing lists (reserved-names and
> > reserved-ranges).
> 
> Heh, I have very much the opposite opinion.  I'd rather have property
> names that match the usage than have the names and values split into
> two properties.  To me, keeping them together is more tasteful.  Queue
> the debate...  :-)

Ideally you want a single property but it's nasty to mix strings and
numbers in a single property like that.

We also have no good APIs to iterate properties, we'd have to add one.

And then there's the property name limits in the spec, charset limits
etc... property names shall not per-se contain data I believe.

Cheers,
Ben.