From 8ac6c7a54ed1b98d142dce24b11c6de6a1e239a5 Mon Sep 17 00:00:00 2001
From: hc <hc@nodka.com>
Date: Tue, 22 Oct 2024 10:36:11 +0000
Subject: [PATCH] 修改4g拨号为QMI,需要在系统里后台执行quectel-CM
---
kernel/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/kernel/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt b/kernel/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
index 0a64633..e8d3096 100644
--- a/kernel/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
+++ b/kernel/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
@@ -63,9 +63,9 @@
able to reclaim it back. Typically that means that the operating
system can use that region to store volatile or cached data that
can be otherwise regenerated or migrated elsewhere.
-inactive (optional) - empty property
- - Indicates the operating system must not active the region. It's only
- do active or inactive for region reusable.
+
+A node must not carry both the no-map and the reusable property as these are
+logically contradictory.
Linux implementation note:
- If a "linux,cma-default" property is present, then Linux will use the
@@ -80,6 +80,8 @@
nodes by adding a memory-region property to the device node.
memory-region (optional) - phandle, specifier pairs to children of /reserved-memory
+memory-region-names (optional) - a list of names, one for each corresponding
+ entry in the memory-region property
Example
-------
--
Gitblit v1.6.2