Revert support for reserved memory regions defined in device tree
Get series with b4
b4 am 1384898504.26969.48.camel@pasglopVersions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Revert support for reserved memory regions defined in device tree
Quoted 10 lines · Grant Likely
Quoted 5 lines
The proposal look good for me. I'm not convinced that we really need the support for 'reg' property, as the fixed memory region is a special case of generic dynamic allocation specified by the size and alloc-ranges, but I assume that there have been already a long discussion about this, so I accept the common consensus.
It is absolutely necessary for some use cases. For example, a framebuffer enabled by firmware and passed onto the kernel for flicker-free boot. Some platforms have fixed regions that cannot be moved up.
Arguably that could be covered with alloc-range and size by making the range be the reg property content basically (and thus size == size of range) but I prefer the reg property, it's a clearer statement of intent.
Cheers,
Ben.