ramoops: support upstream {console,pmsg,ftrace}-size properties
See the latest bindings here:
http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/reserved-memory/ramoops.txt
Upstream supports these properties:
ecc-size
console-size
pmsg-size
ftrace-size
We never actually supported ftrace-size, but we might as well make an
allocation for it in case we want to use it in the future.
For console and pmsg, our custom CrOS kernel code would just make these
the same size as the record size. But now that upstream supports these
properties (and we may backport this to our CrOS kernels), let's
actually utilize them.
I keep the console size at our inflated 256K (from "ramoops: Default
record-size to 256K"), since it's useful. But I reduce pmsg down to
128K, since I don't think we even use it.
Informational note: kernels will not probe this moved
/reserved-memory/ramoops/ node unless they bring in CL:440552 (based on
upstream "ramoops: use DT reserved-memory bindings") to their kernel.
Otherwise, compatibility should not be a problem.
BRANCH=none
BUG=none
CQ-DEPEND=CL:440552
TEST=boot a mostly-vanilla 4.10 and a CrOS 4.4 on Kevin (patches in
flight for supporting '/reserved-memory/ramoops'); check the
properties in /proc/device-tree/reserved-memory/ramoops/; check
that /dev/pstore/console-ramoops{,-0} works as expected
Change-Id: I385abd35f0f595400bb516306d457edb79074fb1
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/439792
Reviewed-by: Julius Werner <jwerner@chromium.org>
4 files changed
