diff options
author | Linaro CI <ci_notify@linaro.org> | 2017-09-24 20:35:18 +0000 |
---|---|---|
committer | Linaro CI <ci_notify@linaro.org> | 2017-09-24 20:35:18 +0000 |
commit | c03adb6848aa7e80ad0c0e46b9f6d96ba0a91822 (patch) | |
tree | 05de08cd2d77fc5697e9e6fc1fae5ef23a1d0a85 /Documentation/ramoops.txt | |
parent | 6ce85a78b6151e8ab2eac57e1447d90d3efb551d (diff) | |
parent | 357fdc8959dc79696d9c43c2a3f7a93e3a503d87 (diff) |
Merge remote-tracking branch 'sumit-lts/lts-4.4.y-hikey' into linux-4.4.y4.4.89-rc1-hikey-20170924
Diffstat (limited to 'Documentation/ramoops.txt')
-rw-r--r-- | Documentation/ramoops.txt | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/Documentation/ramoops.txt b/Documentation/ramoops.txt index 5d8675615e59..9264bcab4099 100644 --- a/Documentation/ramoops.txt +++ b/Documentation/ramoops.txt @@ -45,7 +45,7 @@ corrupt, but usually it is restorable. 2. Setting the parameters -Setting the ramoops parameters can be done in 2 different manners: +Setting the ramoops parameters can be done in 3 different manners: 1. Use the module parameters (which have the names of the variables described as before). For quick debugging, you can also reserve parts of memory during boot @@ -54,7 +54,9 @@ Setting the ramoops parameters can be done in 2 different manners: kernel to use only the first 128 MB of memory, and place ECC-protected ramoops region at 128 MB boundary: "mem=128M ramoops.mem_address=0x8000000 ramoops.ecc=1" - 2. Use a platform device and set the platform data. The parameters can then + 2. Use Device Tree bindings, as described in + Documentation/device-tree/bindings/misc/ramoops.txt. + 3. Use a platform device and set the platform data. The parameters can then be set through that platform data. An example of doing that is: #include <linux/pstore_ram.h> |