[PATCH v3 1/2] dt-bindings: arm: aspeed: sbc: Describe OTP NVMEM provider
From: Prasanth Kumar Padarthi
Date: Fri Nov 20 2026 - 22:41:49 EST
The AST2600 secure boot controller also provides access to its OTP data
region. Reference the NVMEM provider schema and use unevaluatedProperties
so common NVMEM properties are accepted while unknown properties remain
rejected. Cell offsets address OTP data rather than controller registers.
Signed-off-by: Prasanth Kumar Padarthi <prasanth.padarthi10@xxxxxxxxx>
---
Validation: dt-doc-validate and the selected dt_binding_check target passed.
The binding target used dtschema 2026.4 with a local diagnostic lookup fix
for trailing # in schema IDs. No validation rules were disabled. Two
unrelated TI type diagnostics remain; no SBC diagnostics were emitted.
The valid example passed, and an unknown-property negative control failed
as expected.
.../devicetree/bindings/arm/aspeed/aspeed,sbc.yaml | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml b/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml
index b8c5cac..d8e19c2 100644
--- a/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml
+++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml
@@ -13,7 +13,12 @@ maintainers:
description: |
The ASPEED SoCs have a register bank for interacting with the secure boot
- controller.
+ controller. The controller also provides access to the OTP data region
+ through NVMEM. NVMEM cell offsets are byte offsets within the OTP data
+ region, not offsets within the controller register bank.
+
+allOf:
+ - $ref: /schemas/nvmem/nvmem.yaml#
properties:
compatible:
@@ -27,11 +32,12 @@ required:
- compatible
- reg
-additionalProperties: false
+unevaluatedProperties: false
examples:
- |
sbc: secure-boot-controller@1e6f2000 {
compatible = "aspeed,ast2600-sbc";
reg = <0x1e6f2000 0x1000>;
+ read-only;
};
--
2.47.3