Signed-off-by: Mike Shettel <mshettel@xxxxxxxxxxxxxx> --- .../devicetree/bindings/i3c/qcom,geni-i3c.txt | 44 ++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 Documentation/devicetree/bindings/i3c/qcom,geni-i3c.txt diff --git a/Documentation/devicetree/bindings/i3c/qcom,geni-i3c.txt b/Documentation/devicetree/bindings/i3c/qcom,geni-i3c.txt new file mode 100644 index 0000000..8b76fda --- /dev/null +++ b/Documentation/devicetree/bindings/i3c/qcom,geni-i3c.txt @@ -0,0 +1,44 @@ +Bindings for Qualcomm Geni I3C master block +=========================================== + +Required properties: +-------------------- +- compatible: shall be "qcom,geni-i3c" +- clocks: shall reference the se clock +- clock-names: shall contain clock name corresponding to the serial engine +- interrupts: the interrupt line connected to this I3C master +- reg: I3C master registers + +Optional properties: +-------------------- +- se-clock-frequency: Source serial clock frequency to use +- dfs-index: Dynamic frequency scaling table index to use + +Mandatory properties defined by the generic binding (see +Documentation/devicetree/bindings/i3c/i3c.txt for more details): + +- #address-cells: shall be set to 3 +- #size-cells: shall be set to 0 + +Optional properties defined by the generic binding (see +Documentation/devicetree/bindings/i3c/i3c.txt for more details): + +- i2c-scl-hz +- i3c-scl-hz + +I3C device connected on the bus follow the generic description (see +Documentation/devicetree/bindings/i3c/i3c.txt for more details). + +Example: + + i3c-master@0d040000 { + compatible = "qcom,geni-i3c"; + clocks = <&clock_gcc GCC_QUPV3_WRAP0_S0_CLK>; + clock-names = "se"; + interrupts = <GIC_SPI 356 IRQ_TYPE_LEVEL_HIGH>; + reg = <0x0d040000 0x4000>; + #address-cells = <3>; + #size-cells = <0>; + i2c-scl-hz = <100000>; + }; + -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html