Re: Extending /memreserve/ to allow defining descriptions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




David Gibson <david@xxxxxxxxxxxxxxxxxxxxx> writes:
> What you could do is to add properties within the device tree further
> annotating the reservations, with the extra structure essentially just
> acting as an easy-to-parse summary of that.  In fact I know that POWER
> systems firmware use 'reserved-ranges' and 'reserved-names' properties
> for this.  I don't know if anyone else has adopted that though.

We've also been toying with the idea of creating a binding for "named
reserved memory range that should probably show up in debugfs"

I'd also be happy with a standard binding to do it.

-- 
Stewart Smith
OPAL Architect, IBM.

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux