Add 'mode' property to distinguish between 'controller' and 'target' modes.
Signed-off-by: Frank Li <Frank.Li@xxxxxxx>
---
Notes:
Change from v3 to v4
-fix dtb check error
Change from v2 to v3
- using 'mode' distringuish master and target mode
.../devicetree/bindings/i3c/silvaco,i3c-master.yaml | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml b/Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml
index 133855f11b4f5..3af77d143f018 100644
--- a/Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml
+++ b/Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml
@@ -4,7 +4,7 @@
$id: http://devicetree.org/schemas/i3c/silvaco,i3c-master.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
-title: Silvaco I3C master
+title: Silvaco I3C master/target
maintainers:
- Conor Culhane <conor.culhane@xxxxxxxxxxx>
@@ -22,6 +22,15 @@ properties:
interrupts:
maxItems: 1
+ mode:
+ description:
+ Tells Dual-Role I3C controllers that we want to work on a particular
+ mode. In case this attribute isn't passed via DT, I3C controllers
+ should default to 'controller'.
+ $ref: /schemas/types.yaml#/definitions/string
+ enum: [controller, target]
+ default: controller
+
clocks:
items:
- description: system clock
--
2.34.1
