2019-06-03 13:44:50 +08:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-only
|
2012-03-05 19:49:27 +08:00
|
|
|
/*
|
|
|
|
* Based on arch/arm/mm/mmap.c
|
|
|
|
*
|
|
|
|
* Copyright (C) 2012 ARM Ltd.
|
|
|
|
*/
|
|
|
|
|
2017-05-19 23:42:00 +08:00
|
|
|
#include <linux/memblock.h>
|
2021-01-26 20:24:44 +08:00
|
|
|
#include <linux/types.h>
|
2012-03-05 19:49:27 +08:00
|
|
|
|
2021-01-26 20:24:44 +08:00
|
|
|
#include <asm/page.h>
|
2012-03-05 19:49:27 +08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* You really shouldn't be using read() or write() on /dev/mem. This might go
|
|
|
|
* away in the future.
|
|
|
|
*/
|
2014-10-02 22:56:59 +08:00
|
|
|
int valid_phys_addr_range(phys_addr_t addr, size_t size)
|
2012-03-05 19:49:27 +08:00
|
|
|
{
|
2017-05-19 23:42:00 +08:00
|
|
|
/*
|
|
|
|
* Check whether addr is covered by a memory region without the
|
|
|
|
* MEMBLOCK_NOMAP attribute, and whether that region covers the
|
|
|
|
* entire range. In theory, this could lead to false negatives
|
|
|
|
* if the range is covered by distinct but adjacent memory regions
|
|
|
|
* that only differ in other attributes. However, few of such
|
|
|
|
* attributes have been defined, and it is debatable whether it
|
|
|
|
* follows that /dev/mem read() calls should be able traverse
|
|
|
|
* such boundaries.
|
|
|
|
*/
|
|
|
|
return memblock_is_region_memory(addr, size) &&
|
|
|
|
memblock_is_map_memory(addr);
|
2012-03-05 19:49:27 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Do not allow /dev/mem mappings beyond the supported physical range.
|
|
|
|
*/
|
|
|
|
int valid_mmap_phys_addr_range(unsigned long pfn, size_t size)
|
|
|
|
{
|
|
|
|
return !(((pfn << PAGE_SHIFT) + size) & ~PHYS_MASK);
|
|
|
|
}
|