Skip to contentSkip to conversation

pinctrl: msm: Add support for MSM TLMM pinmux

PATCH Superseded Hanumant Singh 2 participants 5 messages Jun 21, 2013 – Jun 27, 2013

Subsystems (2)

v1 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH 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    | 187 +++++
 drivers/pinctrl/Kconfig                            |  10 +
 drivers/pinctrl/Makefile                           |   2 +
 drivers/pinctrl/pinctrl-msm-tlmm-v3.c              | 345 +++++++++
 drivers/pinctrl/pinctrl-msm.c                      | 774 +++++++++++++++++++++
 drivers/pinctrl/pinctrl-msm.h                      | 112 +++
 6 files changed, 1430 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 +187 -0
new file mode 100644
index 0000000..c76777b
@@ -0,0 +1,187 @@
+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.
+  - 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.
+
+  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 value of this property is used as-is to program
+  the pin-controller
+
+  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. The following pin configuration properties are supported by general
+  purpose pins.
+
+  - qcom,gp-pull: Pull up/down configuration.
+  - qcom,gp-drv: Drive strength configuration.
+  - qcom,gp-dir: Pull up/down configuration in power down mode.
+
+  The following pin configurations are properties are supported by SDC pins
+  - qcom,sdc1-clk-pull: Pull up/down configuration SDC1 clock pin.
+  - qcom,sdc1-clk-drv: Drive strength configuration for SDC1 clock pin.
+  - qcom,sdc1-cmd-pull: Pull up/down configuration for SDC1 command pin.
+  - qcom,sdc1-cmd-drv: Drive strength configuration for SDC1 command pin.
+  - qcom,sdc1-data-pull: Pull up/down configuration for SDC1 data pin.
+  - qcom,sdc1-data-drv: Drive strength configuration for SDC1 data pin.
+  - qcom,sdc2-clk-pull: Pull up/down configuration SDC2 clock pin.
+  - qcom,sdc2-clk-drv: Drive strength configuration for SDC2 clock pin.
+  - qcom,sdc2-cmd-pull: Pull up/down configuration for SDC2 command pin.
+  - qcom,sdc2-cmd-drv: Drive strength configuration for SDC2 command pin.
+  - qcom,sdc2-data-pull: Pull up/down configuration for SDC2 data pin.
+  - qcom,sdc2-data-drv: Drive strength configuration for SDC2 data pin.
+
+
+  The values specified by these config properties should be derived from the
+  hardware manual and these values are programmed as-is into the pin
+  pull up/down and driver strength 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 = <0x11400000 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,pin-func = <1>;
+
+			/* Active configuration of bus pins */
+			spi-bus-active: spi-bus-active {
+				qcom,gp-drv = <3>; /* 8 MA */
+				qcom,gp-pull = <0>; /* No PULL */
+			};
+			/* Sleep configuration of bus pins */
+			spi-bus-sleep: spi-bus-sleep {
+				qcom,gp-drv = <0>; /* 2 MA */
+				qcom,gp-pull = <0>; /* No PULL */
+			};
+		};
+
+		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 {
+				qcom,gp-drv = <2>; /* 8 MA */
+				qcom,gp-pull = <0>; /* No PULL */
+			};
+			/* Sleep configuration of cs pin */
+			spi-bus-sleep: spi-bus-sleep {
+				qcom,gp-drv = <0>; /* 2 MA */
+				qcom,gp-pull = <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>;
+		 };
+
+Example 4: Set up the default pin state for spi controller.
+
+	static inline int msm_spi_request_pins{struct msm_spi *dd)
+	{
+		/* ... */
+		dd->pinctrl = devm_pinctrl_get_select_default(&pdev->dev);
+	}
drivers/pinctrl/Kconfig +10 -0
index 8f66924..7cde411 100644
@@ -132,6 +132,16 @@ config PINCTRL_IMX28
 	bool
 	select PINCTRL_MXS
 
+config PINCTRL_MSM
+	depends on OF
+	bool
+	select PINMUX
+	select 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
index 9bdaeb8..80469e4 100644
@@ -26,6 +26,8 @@ obj-$(CONFIG_PINCTRL_FALCON)	+= pinctrl-falcon.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 +345 -0

345 lines not on this page · raw message

drivers/pinctrl/pinctrl-msm.c new file +774 -0

774 lines not on this page · raw message

drivers/pinctrl/pinctrl-msm.h new file +112 -0

112 lines not on this page · raw message

Signature · 6 lines
1.8.2.1

--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
--
#1 lore raw
Quoted 4 lines · Hanumant Singh

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 is really nice.

Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt line 63

Quoted 11 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +11 -0
+  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. The following pin configuration properties are supported by general
+  purpose pins.
+
+  - qcom,gp-pull: Pull up/down configuration.
+  - qcom,gp-drv: Drive strength configuration.
+  - qcom,gp-dir: Pull up/down configuration in power down mode.

Rebase this to use the generic pin config mappings and parsing code that can be found in the "devel" branch of the pinctrl tree.

Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt line 77

Quoted 13 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +13 -0
+  The following pin configurations are properties are supported by SDC pins
+  - qcom,sdc1-clk-pull: Pull up/down configuration SDC1 clock pin.
+  - qcom,sdc1-clk-drv: Drive strength configuration for SDC1 clock pin.
+  - qcom,sdc1-cmd-pull: Pull up/down configuration for SDC1 command pin.
+  - qcom,sdc1-cmd-drv: Drive strength configuration for SDC1 command pin.
+  - qcom,sdc1-data-pull: Pull up/down configuration for SDC1 data pin.
+  - qcom,sdc1-data-drv: Drive strength configuration for SDC1 data pin.
+  - qcom,sdc2-clk-pull: Pull up/down configuration SDC2 clock pin.
+  - qcom,sdc2-clk-drv: Drive strength configuration for SDC2 clock pin.
+  - qcom,sdc2-cmd-pull: Pull up/down configuration for SDC2 command pin.
+  - qcom,sdc2-cmd-drv: Drive strength configuration for SDC2 command pin.
+  - qcom,sdc2-data-pull: Pull up/down configuration for SDC2 data pin.
+  - qcom,sdc2-data-drv: Drive strength configuration for SDC2 data pin.

I don't understand why each sdc thing needs its own definition for everything. Please use the generic pin config bindings, call the generic parser function and then reject if someone tries to config something that is not supported.

Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt line 124

Quoted 13 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +13 -0
+               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,pin-func = <1>;
+
+                       /* Active configuration of bus pins */
+                       spi-bus-active: spi-bus-active {
+                               qcom,gp-drv = <3>; /* 8 MA */
+                               qcom,gp-pull = <0>; /* No PULL */

This would be:

drive-strength = <8>;
bias-disable;

With the generic bindings I believe.

Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt line 187

Quoted 7 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +7 -0
+Example 4: Set up the default pin state for spi controller.
+
+       static inline int msm_spi_request_pins{struct msm_spi *dd)
+       {
+               /* ... */
+               dd->pinctrl = devm_pinctrl_get_select_default(&pdev->dev);
+       }

Nowadays the device core will do this, so this is not any good advice. (See commit ab78029ecc347debbd737f06688d788bd9d60c1d)

I will look closer at this when it uses generic pinconf and generic pinconf DT bindings, let's target v3.12.

Yours,
Linus Walleij

author
#2 lore raw
Quoted 22 lines · Linus Walleij

Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt line 63

Quoted 4 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +4 -0
+
+  - qcom,gp-pull: Pull up/down configuration.
+  - qcom,gp-drv: Drive strength configuration.
+  - qcom,gp-dir: Pull up/down configuration in power down mode.

Rebase this to use the generic pin config mappings and parsing code that can be found in the "devel" branch of the pinctrl tree.

Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt line 77

Quoted 13 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +13 -0
+  The following pin configurations are properties are supported by SDC pins
+  - qcom,sdc1-clk-pull: Pull up/down configuration SDC1 clock pin.
+  - qcom,sdc1-clk-drv: Drive strength configuration for SDC1 clock pin.
+  - qcom,sdc1-cmd-pull: Pull up/down configuration for SDC1 command pin.
+  - qcom,sdc1-cmd-drv: Drive strength configuration for SDC1 command pin.
+  - qcom,sdc1-data-pull: Pull up/down configuration for SDC1 data pin.
+  - qcom,sdc1-data-drv: Drive strength configuration for SDC1 data pin.
+  - qcom,sdc2-clk-pull: Pull up/down configuration SDC2 clock pin.
+  - qcom,sdc2-clk-drv: Drive strength configuration for SDC2 clock pin.
+  - qcom,sdc2-cmd-pull: Pull up/down configuration for SDC2 command pin.
+  - qcom,sdc2-cmd-drv: Drive strength configuration for SDC2 command pin.
+  - qcom,sdc2-data-pull: Pull up/down configuration for SDC2 data pin.
+  - qcom,sdc2-data-drv: Drive strength configuration for SDC2 data pin.
Quoted 5 lines

I don't understand why each sdc thing needs its own definition for everything. Please use the generic pin config bindings, call the generic parser function and then reject if someone tries to config something that is not supported.

The register semantics of SDC1 clk, command, and data lines, pull up and drive strength attributes differ from SDC2 clk, command and data lines.

In general the TLMM v3 has more pin types then just the general/multi purpose(gp) and SDC pin types above.
There are some pin types on the TLMM, whose config attributes do not fall under the cattegories supported by generic pin config. These attributes in some cases happen to be protocol specific. Hence I would prefer to go with a custom config pack and unpack implementation rather then the generic one.

Quoted 11 lines

Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt line 187

Quoted 8 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +7 -0
+Example 4: Set up the default pin state for spi controller.
+
+       static inline int msm_spi_request_pins{struct msm_spi *dd)
+       {
+               /* ... */
+               dd->pinctrl = devm_pinctrl_get_select_default(&pdev->dev);
+       }

Nowadays the device core will do this, so this is not any good advice. (See commit ab78029ecc347debbd737f06688d788bd9d60c1d)

I will modify this.

Quoted 7 lines

I will look closer at this when it uses generic pinconf and generic pinconf DT bindings, let's target v3.12.

Yours,
Linus Walleij

Signature · 4 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, hosted by The Linux Foundation
-- 
#3 lore raw
Quoted 16 lines · hanumant
Quoted 14 lines · Linus Walleij
Quoted 13 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +13 -0
+  The following pin configurations are properties are supported by SDC pins
+  - qcom,sdc1-clk-pull: Pull up/down configuration SDC1 clock pin.
+  - qcom,sdc1-clk-drv: Drive strength configuration for SDC1 clock pin.
+  - qcom,sdc1-cmd-pull: Pull up/down configuration for SDC1 command pin.
+  - qcom,sdc1-cmd-drv: Drive strength configuration for SDC1 command pin.
+  - qcom,sdc1-data-pull: Pull up/down configuration for SDC1 data pin.
+  - qcom,sdc1-data-drv: Drive strength configuration for SDC1 data pin.
+  - qcom,sdc2-clk-pull: Pull up/down configuration SDC2 clock pin.
+  - qcom,sdc2-clk-drv: Drive strength configuration for SDC2 clock pin.
+  - qcom,sdc2-cmd-pull: Pull up/down configuration for SDC2 command pin.
+  - qcom,sdc2-cmd-drv: Drive strength configuration for SDC2 command pin.
+  - qcom,sdc2-data-pull: Pull up/down configuration for SDC2 data pin.
+  - qcom,sdc2-data-drv: Drive strength configuration for SDC2 data pin.
Quoted 7 lines
Quoted 4 lines

I don't understand why each sdc thing needs its own definition for everything. Please use the generic pin config bindings, call the generic parser function and then reject if someone tries to config something that is not supported.

The register semantics of SDC1 clk, command, and data lines, pull up and drive strength attributes differ from SDC2 clk, command and data lines.

The register semantics does not have anything to do with the representation in the device tree. The register semantics is a matter for the driver, the device tree tells how to configure that driver, the idea is not to name all species of config registers in the device tree but to configure them, logically.

Quoted 4 lines

In general the TLMM v3 has more pin types then just the general/multi purpose(gp) and SDC pin types above.
There are some pin types on the TLMM, whose config attributes do not fall under the cattegories supported by generic pin config.

One does not exclude the other. Some aspect of a pin may be configured using the generic bindings, some aspect need vendor-specific extensions.

Quoted 3 lines

These attributes in some cases happen to be protocol specific. Hence I would prefer to go with a custom config pack and unpack implementation rather then the generic one.

I disagree, but I'm open to negotiations :-)

Yours,
Linus Walleij

author
#4 lore raw
Quoted 22 lines · Linus Walleij
Quoted 21 lines · hanumant
Quoted 18 lines · Linus Walleij

Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt line 77

Quoted 13 lines
Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt new file +13 -0
+  The following pin configurations are properties are supported by SDC pins
+  - qcom,sdc1-clk-pull: Pull up/down configuration SDC1 clock pin.
+  - qcom,sdc1-clk-drv: Drive strength configuration for SDC1 clock pin.
+  - qcom,sdc1-cmd-pull: Pull up/down configuration for SDC1 command pin.
+  - qcom,sdc1-cmd-drv: Drive strength configuration for SDC1 command pin.
+  - qcom,sdc1-data-pull: Pull up/down configuration for SDC1 data pin.
+  - qcom,sdc1-data-drv: Drive strength configuration for SDC1 data pin.
+  - qcom,sdc2-clk-pull: Pull up/down configuration SDC2 clock pin.
+  - qcom,sdc2-clk-drv: Drive strength configuration for SDC2 clock pin.
+  - qcom,sdc2-cmd-pull: Pull up/down configuration for SDC2 command pin.
+  - qcom,sdc2-cmd-drv: Drive strength configuration for SDC2 command pin.
+  - qcom,sdc2-data-pull: Pull up/down configuration for SDC2 data pin.
+  - qcom,sdc2-data-drv: Drive strength configuration for SDC2 data pin.

I don't understand why each sdc thing needs its own definition for everything. Please use the generic pin config bindings, call the generic parser function and then reject if someone tries to config something that is not supported.

Quoted 8 lines
Quoted 2 lines

The register semantics of SDC1 clk, command, and data lines, pull up and drive strength attributes differ from SDC2 clk, command and data lines.

The register semantics does not have anything to do with the representation in the device tree. The register semantics is a matter for the driver, the device tree tells how to configure that driver, the idea is not to name all species of config registers in the device tree but to configure them, logically.

Fair enough. I think this is possible to do.

Quoted 10 lines
Quoted 5 lines

In general the TLMM v3 has more pin types then just the general/multi purpose(gp) and SDC pin types above.
There are some pin types on the TLMM, whose config attributes do not fall under the cattegories supported by generic pin config.

One does not exclude the other. Some aspect of a pin may be configured using the generic bindings, some aspect need vendor-specific extensions.

Quoted 5 lines
Quoted 3 lines

These attributes in some cases happen to be protocol specific. Hence I would prefer to go with a custom config pack and unpack implementation rather then the generic one.

I disagree, but I'm open to negotiations :-)

How does this sound?. If the attributes of a pin type can be defined using the generic configs, I will use the generic configs and parser. If the attributes are entirely protocol/MSM specific, I will use custom configs and parsers. In terms of attributes of pins, all the pin types on the TLMM fall into either one of those categories, but never in both.

Thanks
Hanumant

Signature · 4 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, hosted by The Linux Foundation
--