Qualcomm Technologies, Inc. SDM670 TLMM block This binding describes the Top Level Mode Multiplexer block found in the SDM670 platform. - compatible: Usage: required Value type: Definition: must be "qcom,sdm670-pinctrl" - reg: Usage: required Value type: Definition: the base address and size of the TLMM register space provided as "pinctrl_regs", optional base address of PDC mux selection registers provided as "pdc_regs" and optional base address of shared SPI config registers provided as "spi_cfg_regs". - reg-names: Usage: required Value type: Definition: Provides labels for the reg property. - interrupts: Usage: required Value type: Definition: should specify the TLMM summary IRQ. - interrupt-controller: Usage: required Value type: Definition: identifies this node as an interrupt controller - #interrupt-cells: Usage: required Value type: Definition: must be 2. Specifying the pin number and flags, as defined in - gpio-controller: Usage: required Value type: Definition: identifies this node as a gpio controller - #gpio-cells: Usage: required Value type: Definition: must be 2. Specifying the pin number and flags, as defined in Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for a general description of GPIO and interrupt bindings. Please refer to pinctrl-bindings.txt in this directory for details of the common pinctrl bindings used by client devices, including the meaning of the phrase "pin configuration node". The pin configuration nodes act as a container for an arbitrary number of subnodes. Each of these subnodes represents some desired configuration for a pin, a group, or a list of pins or groups. This configuration can include the mux function to select on those pin(s)/group(s), and various pin configuration parameters, such as pull-up, drive strength, etc. PIN CONFIGURATION NODES: The name of each subnode is not important; all subnodes should be enumerated and processed purely based on their content. Each subnode only affects those parameters that are explicitly listed. In other words, a subnode that lists a mux function but no pin configuration parameters implies no information about any pin configuration parameters. Similarly, a pin subnode that describes a pullup parameter implies no information about e.g. the mux function. The following generic properties as defined in pinctrl-bindings.txt are valid to specify in a pin configuration subnode: - pins: Usage: required Value type: Definition: List of gpio pins affected by the properties specified in this subnode. Valid pins are: gpio0-gpio149 Supports mux, bias and drive-strength sdc1_clk, sdc1_cmd, sdc1_data sdc2_clk, sdc2_cmd, sdc2_data sdc1_rclk Supports bias and drive-strength - function: Usage: required Value type: Definition: Specify the alternative function to be configured for the specified pins. Functions are only valid for gpio pins. Valid values are: qup0, qup9, qdss_cti, ddr_pxi0, ddr_bist, atest_tsens2, vsense_trigger, atest_usb1, qup_l4, GP_PDM1, qup_l5, mdp_vsync, qup_l6, wlan2_adc1, atest_usb11, ddr_pxi2, edp_lcd, dbg_out, wlan2_adc0, atest_usb10, m_voc, tsif1_sync, ddr_pxi3, cam_mclk, pll_bypassnl, qdss_gpio0, pll_reset, qdss_gpio1, qdss_gpio2, qdss_gpio3, cci_i2c, qup1, gpio - bias-disable: Usage: optional Value type: Definition: The specified pins should be configued as no pull. - bias-pull-down: Usage: optional Value type: Definition: The specified pins should be configued as pull down. - bias-pull-up: Usage: optional Value type: Definition: The specified pins should be configued as pull up. - output-high: Usage: optional Value type: Definition: The specified pins are configured in output mode, driven high. Not valid for sdc pins. - output-low: Usage: optional Value type: Definition: The specified pins are configured in output mode, driven low. Not valid for sdc pins. - drive-strength: Usage: optional Value type: Definition: Selects the drive strength for the specified pins, in mA. Valid values are: 2, 4, 6, 8, 10, 12, 14 and 16 Example: tlmm: pinctrl@03400000 { compatible = "qcom,sdm670-pinctrl"; reg = <0x03400000 0xc00000>, <0x179900f0 0x60>; reg-names = "pinctrl_regs", "spi_cfg_regs"; interrupts = <0 208 0>; gpio-controller; #gpio-cells = <2>; interrupt-controller; #interrupt-cells = <2>; };