diff options
| author | Linaro CI <ci_notify@linaro.org> | 2017-12-11 23:04:00 +0000 |
|---|---|---|
| committer | Linaro CI <ci_notify@linaro.org> | 2017-12-11 23:04:00 +0000 |
| commit | 23cbdfaa6d8f83dff03cd0b04d9af8051a11c126 (patch) | |
| tree | 812d7df7bdf521b896b283a8a5c0bd2723263468 /Documentation/ramoops.txt | |
| parent | 60c2da397c68643ac1b187a90f1c9ef29214443d (diff) | |
| parent | 8466c55d9fbc79c97cfe36a376f10d4805868399 (diff) | |
Merge remote-tracking branch 'sumit-lts/lts-4.4.y-hikey' into linux-4.4.y4.4.106-rc1-hikey-20171211-73
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> |