On a typical end product, a vendor may choose to secure some regions in
the NAND memory which are supposed to stay intact between FW upgrades.
The access to those regions will be blocked by a secure element like
Trustzone. So the normal world software like Linux kernel should not
touch these regions (including reading).
So this series adds a property for declaring such secure regions in DT
so that the driver can skip touching them. While at it, the Qcom NANDc
DT binding is also converted to YAML format.
Thanks,
Mani
Changes in v6:
* Made use of "size" of the regions for comparision
* Used "secure" instead of "sec"
* Fixed the sizeof parameter in of_get_nand_secure_regions()
Changes in v5:
* Switched to "uint64-matrix" as suggested by Rob
* Moved the whole logic from qcom driver to nand core as suggested by Boris
Changes in v4:
* Used "uint32-matrix" instead of "uint32-array" as per Rob's review.
* Collected Rob's review tag for binding conversion patch
Changes in v3:
* Removed the nand prefix from DT property and moved the property parsing
logic before nand_scan() in driver.
Changes in v2:
* Moved the secure-regions property to generic NAND binding as a NAND
chip property and renamed it as "nand-secure-regions".
Manivannan Sadhasivam (3):
dt-bindings: mtd: Convert Qcom NANDc binding to YAML
dt-bindings: mtd: Add a property to declare secure regions in NAND
chips
mtd: rawnand: Add support for secure regions in NAND memory
.../bindings/mtd/nand-controller.yaml | 7 +
.../devicetree/bindings/mtd/qcom,nandc.yaml | 196 ++++++++++++++++++
.../devicetree/bindings/mtd/qcom_nandc.txt | 142 -------------
drivers/mtd/nand/raw/nand_base.c | 111 ++++++++++
include/linux/mtd/rawnand.h | 4 +
5 files changed, 318 insertions(+), 142 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mtd/qcom,nandc.yaml
delete mode 100644 Documentation/devicetree/bindings/mtd/qcom_nandc.txt
--
2.25.1
