On Wed, Mar 14, 2018 at 05:58:46PM -0600, Karthikeyan Ramasubramanian wrote: > Add device tree binding support for the QCOM GENI SE driver. > > Signed-off-by: Karthikeyan Ramasubramanian <kramasub@xxxxxxxxxxxxxx> > Signed-off-by: Sagar Dharia <sdharia@xxxxxxxxxxxxxx> > Signed-off-by: Girish Mahadevan <girishm@xxxxxxxxxxxxxx> > --- > .../devicetree/bindings/soc/qcom/qcom,geni-se.txt | 123 +++++++++++++++++++++ > 1 file changed, 123 insertions(+) > create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.txt > > diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.txt b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.txt > new file mode 100644 > index 0000000..b71b5df > --- /dev/null > +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.txt > @@ -0,0 +1,123 @@ > +Qualcomm Technologies, Inc. GENI Serial Engine QUP Wrapper Controller > + > +Generic Interface (GENI) based Qualcomm Universal Peripheral (QUP) wrapper > +is a programmable module for supporting a wide range of serial interfaces > +like UART, SPI, I2C, I3C, etc. A single QUP module can provide upto 8 Serial > +Interfaces, using its internal Serial Engines. The GENI Serial Engine QUP > +Wrapper controller is modeled as a node with zero or more child nodes each > +representing a serial engine. > + > +Required properties: > +- compatible: Must be "qcom,geni-se-qup". > +- reg: Must contain QUP register address and length. > +- clock-names: Must contain "m-ahb" and "s-ahb". > +- clocks: AHB clocks needed by the device. > + > +Required properties if child node exists: > +- #address-cells: Must be <1> for Serial Engine Address > +- #size-cells: Must be <1> for Serial Engine Address Size > +- ranges: Must be present > + > +Properties for children: > + > +A GENI based QUP wrapper controller node can contain 0 or more child nodes > +representing serial devices. These serial devices can be a QCOM UART, I2C > +controller, SPI controller, or some combination of aforementioned devices. > +Please refer below the child node definitions for the supported serial > +interface protocols. > + > +Qualcomm Technologies Inc. GENI Serial Engine based I2C Controller > + > +Required properties: > +- compatible: Must be "qcom,geni-i2c". > +- reg: Must contain QUP register address and length. > +- interrupts: Must contain I2C interrupt. > +- clock-names: Must contain "se". > +- clocks: Serial engine core clock needed by the device. > +- #address-cells: Must be <1> for I2C device address. > +- #size-cells: Must be <0> as I2C addresses have no size component. > + > +Optional property: > +- clock-frequency: Desired I2C bus clock frequency in Hz. > + When missing default to 400000Hz. > + > +Child nodes should conform to I2C bus binding as described in i2c.txt. > + > +Qualcomm Technologies Inc. GENI Serial Engine based UART Controller > + > +Required properties: > +- compatible: Must be "qcom,geni-debug-uart". > +- reg: Must contain UART register location and length. > +- interrupts: Must contain UART core interrupts. > +- clock-names: Must contain "se". > +- clocks: Serial engine core clock needed by the device. > + > +Qualcomm Technologies Inc. GENI Serial Engine based SPI Controller > + > +Required properties: > +- compatible: Must contain "qcom,geni-spi". > +- reg: Must contain SPI register location and length. > +- interrupts: Must contain SPI controller interrupts. > +- clock-names: Must contain "se". > +- clocks: Serial engine core clock needed by the device. > +- spi-max-frequency: Specifies maximum SPI clock frequency, units - Hz. > +- #address-cells: Must be <1> to define a chip select address on > + the SPI bus. > +- #size-cells: Must be <0>. > + > +Optional property: > +- qcom,rt: Indicates if the framework worker thread for this > + controller device should have real-time priority. Sounds like a Linux issue, not a DT property. Given you have no driver yet, I'd drop this for now at least. With that, Reviewed-by: Rob Herring <robh@xxxxxxxxxx> Rob -- 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
