[PATCH v3 5/7] image-fdt: save no-map parameter of reserve-memory

[Patrick DELAUNAY]

Hi Simon,

On 4/29/21 6:10 PM, Simon Glass wrote:
> Hi Patrick,
>
> On Wed, 28 Apr 2021 at 03:23, Patrick Delaunay
> <patrick.delaunay at foss.st.com> wrote:
>> Save the no-map information present in 'reserved-memory' node to allow
>> correct handling when the MMU is configured in board to avoid
>> speculative access.
>>
>> Signed-off-by: Patrick Delaunay <patrick.delaunay at foss.st.com>
>> ---
>>
>> (no changes since v1)
>>
>>   common/image-fdt.c | 23 +++++++++++++++--------
>>   1 file changed, 15 insertions(+), 8 deletions(-)
> Where is no-map documented?


In linux: 
Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt

in U-Boot: doc/device-tree-bindings/reserved-memory/reserved-memory.txt:55

no-map (optional) - empty property
     - Indicates the operating system must not create a virtual mapping
       of the region as part of its standard mapping of system memory,
       nor permit speculative access to it under any circumstances other
       than under the control of the device driver using the region.


But I will add this indication in the commit message.


>
> Reviewed-by: Simon Glass <sjg at chromium.org>


Thanks,

Patrick