| .. | .. |
|---|
| 63 | 63 | able to reclaim it back. Typically that means that the operating |
|---|
| 64 | 64 | system can use that region to store volatile or cached data that |
|---|
| 65 | 65 | can be otherwise regenerated or migrated elsewhere. |
|---|
| 66 | | -inactive (optional) - empty property |
|---|
| 67 | | - - Indicates the operating system must not active the region. It's only |
|---|
| 68 | | - do active or inactive for region reusable. |
|---|
| 66 | + |
|---|
| 67 | +A node must not carry both the no-map and the reusable property as these are |
|---|
| 68 | +logically contradictory. |
|---|
| 69 | 69 | |
|---|
| 70 | 70 | Linux implementation note: |
|---|
| 71 | 71 | - If a "linux,cma-default" property is present, then Linux will use the |
|---|
| .. | .. |
|---|
| 80 | 80 | nodes by adding a memory-region property to the device node. |
|---|
| 81 | 81 | |
|---|
| 82 | 82 | memory-region (optional) - phandle, specifier pairs to children of /reserved-memory |
|---|
| 83 | +memory-region-names (optional) - a list of names, one for each corresponding |
|---|
| 84 | + entry in the memory-region property |
|---|
| 83 | 85 | |
|---|
| 84 | 86 | Example |
|---|
| 85 | 87 | ------- |
|---|