pinctrl: msm: Add support for MSM TLMM pinmux
Subsystems (2)
PATCH v3 1/1 pinctrl: msm: Add support for MSM TLMM pinmux
Add a new device tree enabled pinctrl driver for Qualcomm MSM SoC's. This driver provides an extensible framework to interface all MSM's that use a TLMM pinmux, with the pinctrl subsytem.
This driver is split into two parts: the pinctrl interface and the TLMM version specific implementation. The pinctrl interface parses the device tree and registers with the pinctrl subsytem. The TLMM version specific implementation supports pin configuration/register programming for the different pin types present on a given TLMM pinmux version.
Add support only for TLMM version 3 pinmux right now, as well as, only two of the different pin types present on the TLMM v3 pinmux.
Pintype 1: General purpose pins.
Pintype 2: SDC pins.
--- .../devicetree/bindings/pinctrl/msm-pinctrl.txt | 181 +++++ drivers/pinctrl/Kconfig | 10 + drivers/pinctrl/Makefile | 2 + drivers/pinctrl/pinctrl-msm-tlmm-v3.c | 330 +++++++++ drivers/pinctrl/pinctrl-msm.c | 751 +++++++++++++++++++++ drivers/pinctrl/pinctrl-msm.h | 97 +++ 6 files changed, 1371 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt create mode 100644 drivers/pinctrl/pinctrl-msm-tlmm-v3.c create mode 100644 drivers/pinctrl/pinctrl-msm.c create mode 100644 drivers/pinctrl/pinctrl-msm.h
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +181 -0
@@ -0,0 +1,181 @@ +MSM TLMM pinmux controller + +Qualcomm MSM integrates a GPIO and Pin mux/config hardware, (TOP Level Mode +Multiplexper in short TLMM). It controls the input/output settings on the +available pads/pins and also provides ability to multiplex and configure the +output of various on-chip controllers onto these pads. The pins are also of +different types, encapsulating different functions and having differing register +semantics. + +Required Properties: +- compatible: should be one of the following. + - "qcom,msm-tlmm-v3": for MSM with TLMM version 3. + +- reg: Base address of the pin controller hardware module and length of + the address space it occupies. + +- Pin types as child nodes: Pin types supported by a particular controller + instance are represented as child nodes of the controller node. Each + pin type node must contain following properties: + +Required Properties + - qcom,pin-type-*: identifies the pin type. Pin types supported are + qcom,pin-type-gp (General purpose) + qcom,pin-type-sdc (SDC) + - qcom,pin-cells: number of cells in the pin type specifier. + - qcom,num-pins: number of pins of given type present on the MSM. + +- Pin groups as child nodes: The pin mux (selecting pin function + mode) and pin config (pull up/down, driver strength, direction) settings are + represented as child nodes of the pin-controller node. There is no limit on + the count of these child nodes. + + Required Properties + -qcom,pins: phandle specifying pin type and a pin number. + -qcom,num-grp-pins: number of pins in the group. + + Optional Properties + -qcom,pin-func: function setting for the pin group. + + The child node should contain a list of pin(s) on which a particular pin + function selection or pin configuration (or both) have to applied. This + list of pins is specified using the property name "qcom,pins". There + should be atleast one pin specfied for this property and there is no upper + limit on the count of pins that can be specified. The pins are specified + using the pintype phandle and the pin number within that pintype. + + The pin function selection that should be applied on the pins listed in the + child node is specified using the "qcom,pin-func" property. The value + of this property that should be applied to each of the pins listed in the + "qcom,pins" property, should be picked from the hardware manual of the SoC. + This property is optional in the child node if no specific function + selection is desired for the pins listed in the child node or if the pin is + to be used for bit bang. + + The pin group node must additionally have a pin configuration node as its own + child node. There can be more then one such configuration node for a pin group + node. There can be one or more configurations within the configuration + node. These configurations are applied to all pins mentoned above using the + "qcom,pins" property. These configurations are specific to the pintype of the + pins. + For the pin configuration properties supported by general purpose pins as well + as SDC pins lookup Documentation/devicetree/bindings/pinctrl-bindings.txt + + The values specified by these config properties should be derived from the + hardware manual and these values are programmed as-is into the pin config + register of the pin-controller. + + NOTE: A pin group node should be formed for all pins that are going to have + the same function and configuration settings. If a subset of pins to be used + by a client require different function or configuration settings or both + then they should be modelled as a separate pin group node to be used by + the client. + + The client nodes that require a particular pin function selection and/or + pin configuration should use the bindings listed in the "pinctrl-bindings.txt" + file. + +Example 1: A pin-controller node with pin types + + pinctrl@fd5110000 { + compatible = "qcom,msm-tlmm-v3"; + reg = <0xfd5110000 0x4000>; + + /* General purpose pin type */ + gp: gp { + qcom,pin-type-gp; + qcom,num-pins = <117>; + #qcom,pin-cells = <1>; + }; + }; + +Example 2: Spi pin entries within the pincontroller node + pinctrl@fd511000 { + .... + .. + spi-bus { + /* + * MOSI, MISO and CLK lines + * all sharing same function and config + * settings for each configuration node. + */ + qcom,pins = <&gp 0>, <&gp 1>, <&gp 3>; + qcom,num-grp-pins = <3>; + qcom,pin-func = <1>; + + /* Active configuration of bus pins */ + spi-bus-active: spi-bus-active { + /* + * Property names as specified in + * pinctrl-bindings.txt + */ + drive-strength = <8>; /* 8 MA */ + bias-disable; /* No PULL */ + }; + /* Sleep configuration of bus pins */ + spi-bus-sleep: spi-bus-sleep { + /* + * Property values as specified in HW + * manual. + */ + drive-strength = <2>; /* 2 MA */ + bias-disable; + }; + }; + + spi-cs { + /* + * Chip select for SPI + * different config + * settings as compared to bus pins. + */ + qcom,pins = <&Gp 2>; + qcom,num-grp-pins = <1>; + qcom,pin-func = <1>; + + /* Active configuration of cs pin */ + spi-cs-active: spi-cs-active { + /* + * Property names as specified in + * pinctrl-bindings.txt + */ + drive-strength = <4>; /* 4 MA */ + bias-disable; /* No PULL */ + }; + /* Sleep configuration of cs pin */ + spi-bus-sleep: spi-bus-sleep { + /* + * Property values as specified in HW + * manual. + */ + drive-strength = <2>; /* 2 MA */ + bias-disable = <0>; /* No PULL */ + }; + }; + }; + +Example 3: A SPI client node that supports 'active' and 'sleep' states. + + spi_0: spi@f9923000 { /* BLSP1 QUP1 */ + compatible = "qcom,spi-qup-v2"; + #address-cells = <1>; + #size-cells = <0>; + reg-names = "spi_physical", "spi_bam_physical"; + reg = <0xf9923000 0x1000>, + <0xf9904000 0xF000>; + interrupt-names = "spi_irq", "spi_bam_irq"; + interrupts = <0 95 0>, <0 238 0>; + spi-max-frequency = <19200000>; + + /* pins used by spi controllers */ + pinctrl-names = "default", "sleep"; + pinctrl-0 = <&spi-bus-active &spi-cs-active>; + pinctrl-1 = <&spi-bus-sleep &spi-cs-sleep>; + + qcom,infinite-mode = <0>; + qcom,use-bam; + qcom,ver-reg-exists; + qcom,bam-consumer-pipe-index = <12>; + qcom,bam-producer-pipe-index = <13>; + }; +
drivers/pinctrl/Kconfig +10 -0
@@ -133,6 +133,16 @@ config PINCTRL_IMX28 bool select PINCTRL_MXS +config PINCTRL_MSM + depends on OF + bool + select PINMUX + select GENERIC_PINCONF + +config PINCTRL_MSM_TLMM_V3 + bool + select PINCTRL_MSM + config PINCTRL_NOMADIK bool "Nomadik pin controller driver" depends on ARCH_U8500 || ARCH_NOMADIK
drivers/pinctrl/Makefile +2 -0
@@ -27,6 +27,8 @@ obj-$(CONFIG_PINCTRL_MMP2) += pinctrl-mmp2.o obj-$(CONFIG_PINCTRL_MXS) += pinctrl-mxs.o obj-$(CONFIG_PINCTRL_IMX23) += pinctrl-imx23.o obj-$(CONFIG_PINCTRL_IMX28) += pinctrl-imx28.o +obj-$(CONFIG_PINCTRL_MSM) += pinctrl-msm.o +obj-$(CONFIG_PINCTRL_MSM_TLMM_V3) += pinctrl-msm-tlmm-v3.o obj-$(CONFIG_PINCTRL_NOMADIK) += pinctrl-nomadik.o obj-$(CONFIG_PINCTRL_STN8815) += pinctrl-nomadik-stn8815.o obj-$(CONFIG_PINCTRL_DB8500) += pinctrl-nomadik-db8500.o
drivers/pinctrl/pinctrl-msm-tlmm-v3.c new file +330 -0
330 lines not on this page · raw message
drivers/pinctrl/pinctrl-msm.c new file +751 -0
751 lines not on this page · raw message
drivers/pinctrl/pinctrl-msm.h new file +97 -0
97 lines not on this page · raw message
Signature · 3 lines
Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. --
drivers/pinctrl/pinctrl-msm.c line 750
Quoted 3 lines · Hanumant Singh
drivers/pinctrl/pinctrl-msm.c new file +3
-0+ +MODULE_AUTHOR ("Hanumant Singh <[email protected]>" ); +MODULE_LICENSE ("GPLv2" );
Doesn't this need to be "GPL v2"?
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation