Linux kernel documentation tree maintained by Jonathan Corbet http://mirrors.hust.edu.cn/git/lwn.git/atom?h=doc%2F4.9 2016-08-05T18:21:36+00:00 2016-08-05T18:21:36+00:00 Kees Cook keescook@chromium.org 2016-07-30T01:11:32+00:00 urn:sha1:529182e204db083cb7bda832d1c5c6d9278ba1cb Instead of a ramoops-specific node, use a child node of /reserved-memory. This requires that of_platform_device_create() be explicitly called for the node, though, since "/reserved-memory" does not have its own "compatible" property. Suggested-by: Rob Herring <robh@kernel.org> Signed-off-by: Kees Cook <keescook@chromium.org> Acked-by: Rob Herring <robh@kernel.org> 2014-03-04T08:44:23+00:00 Grant Likely grant.likely@linaro.org 2014-02-28T13:42:46+00:00 urn:sha1:f08ad1deaaf83b7e7369716949b34dadc530be01 Reserved memory nodes allow for the reservation of static (fixed address) regions, or dynamically allocated regions for a specific purpose. [joshc: Based on binding document proposed (in non-patch form) here: http://lkml.kernel.org/g/20131030134702.19B57C402A0@trevor.secretlab.ca adapted to support #memory-region-cells] Signed-off-by: Josh Cartwright <joshc@codeaurora.org> [mszyprow: removed #memory-region-cells property] Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> [grant.likely: removed residual #memory-region-cells example] Signed-off-by: Grant Likely <grant.likely@linaro.org>