Qualcomm SM8150 TLMM block This binding describes the Top Level Mode Multiplexer block found in the QCS404 platform. - compatible: Usage: required Value type: Definition: must be "qcom,sm8150-pinctrl" - reg: Usage: required Value type: Definition: the base address and size of the north, south, west and east TLMM tiles. - reg-names: Usage: required Value type: Defintiion: names for the cells of reg, must contain "north", "south" "west" and "east". - 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 - gpio-ranges: Usage: required Value type: Definition: see ../gpio/gpio.txt - gpio-reserved-ranges: Usage: optional Value type: Definition: see ../gpio/gpio.txt 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 ufs_reset 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: adsp_ext, agera_pll, aoss_cti, ddr_pxi2, atest_char, atest_char0, atest_char1, atest_char2, atest_char3, audio_ref, atest_usb1, atest_usb2, atest_usb10, atest_usb11, atest_usb12, atest_usb13, atest_usb20, atest_usb21, atest_usb22, atest_usb2, atest_usb23, btfm_slimbus, cam_mclk, cci_async, cci_i2c, cci_timer0, cci_timer1, cci_timer2, cci_timer3, cci_timer4, cri_trng, cri_trng0, cri_trng1, dbg_out, ddr_bist, ddr_pxi0, ddr_pxi1, ddr_pxi3, edp_hot, edp_lcd, emac_phy, emac_pps, gcc_gp1, gcc_gp2, gcc_gp3, gpio, hs1_mi2s, hs2_mi2s, hs3_mi2s, jitter_bist, lpass_slimbus, mdp_vsync, mdp_vsync0, mdp_vsync1, mdp_vsync2, mdp_vsync3, mss_lte, m_voc, nav_pps, pa_indicator, pci_e0, phase_flag, pll_bypassnl, pll_bist, pci_e1, pll_reset, pri_mi2s, pri_mi2s_ws, prng_rosc, qdss, qdss_cti, qlink_request, qlink_enable, qspi0, qspi1, qspi2, qspi3, qspi_clk, qspi_cs, qua_mi2s, qup0, qup1, qup2, qup3, qup4, qup5, qup6, qup7, qup8, qup9, qup10, qup11, qup12, qup13, qup14, qup15, qup16, qup17, qup18, qup19, qup_l4, qup_l5, qup_l6, rgmii, sdc4, sd_write, sec_mi2s, spkr_i2s, sp_cmu, ter_mi2s, tgu_ch0, tgu_ch1, tgu_ch2, tgu_ch3, tsense_pwm1, tsense_pwm2, tsif1, tsif2, uim1, uim2, uim_batt, usb2phy_ac, usb_phy, vfr_1, vsense_trigger, wlan1_adc0, wlan1_adc1, wlan2_adc0, wlan2_adc1, wmss_reset - 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@3000000 { compatible = "qcom,sm8150-pinctrl"; reg = <0x03100000 0x300000>, <0x03500000 0x300000>, <0x03900000 0x300000>, <0x03D00000 0x300000>; reg-names = "west", "east", "north", "south"; interrupts = ; gpio-controller; #gpio-cells = <2>; gpio-ranges = <&tlmm 0 0 175>; gpio-reserved-ranges = <0 4>, <126 4>; interrupt-controller; #interrupt-cells = <2>; };