Skip to contentSkip to conversation

Add GPIO support for PM7325, PM8350c, PMK8350 and PMR735A

PATCH Superseded satya priya 4 participants 10 messages Apr 1, 2021 – May 6, 2021

Subsystems (6)

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

v2 cover Add GPIO support for PM7325, PM8350c, PMK8350 and PMR735A

satya priya (3):
pinctrl: qcom: spmi-gpio: Add support for four variants
dt-bindings: pinctrl: qcom-pmic-gpio: Update the binding to add four
new variants
dt-bindings: pinctrl: qcom-pmic-gpio: Convert qcom pmic gpio bindings
to YAML

 .../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 272 --------------------
 .../bindings/pinctrl/qcom,pmic-gpio.yaml           | 281 +++++++++++++++++++++
 drivers/pinctrl/qcom/pinctrl-spmi-gpio.c           |   4 +
 3 files changed, 285 insertions(+), 272 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
 create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member 
of Code Aurora Forum, hosted by The Linux Foundation
#1 lore raw

PATCH v2 1/3 pinctrl: qcom: spmi-gpio: Add support for four variants

Add PM7325, PM8350c, PMK8350 and PMR735A compatibles for GPIO support.

---
Changes in V2:
- No change.

 drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 4 ++++
 1 file changed, 4 insertions(+)
drivers/pinctrl/qcom/pinctrl-spmi-gpio.c +4 -0
index 9801c71..90f4f78 100644
@@ -1131,6 +1131,10 @@ static const struct of_device_id pmic_gpio_of_match[] = {
 	{ .compatible = "qcom,pm6150l-gpio", .data = (void *) 12 },
 	/* pmx55 has 11 GPIOs with holes on 3, 7, 10, 11 */
 	{ .compatible = "qcom,pmx55-gpio", .data = (void *) 11 },
+	{ .compatible = "qcom,pm7325-gpio", .data = (void *) 10 },
+	{ .compatible = "qcom,pm8350c-gpio", .data = (void *) 9 },
+	{ .compatible = "qcom,pmk8350-gpio", .data = (void *) 4 },
+	{ .compatible = "qcom,pmr735a-gpio", .data = (void *) 4 },
 	{ },
 };
 
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member 
of Code Aurora Forum, hosted by The Linux Foundation
#2 lore raw

Re: [PATCH V2 1/3] pinctrl: qcom: spmi-gpio: Add support for four variants

Quoted 17 lines · satya priya

Add PM7325, PM8350c, PMK8350 and PMR735A compatibles for GPIO support.

---
Changes in V2:
- No change.

 drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 4 ++++
 1 file changed, 4 insertions(+)
drivers/pinctrl/qcom/pinctrl-spmi-gpio.c +0 -0
index 9801c71..90f4f78 100644

drivers/pinctrl/qcom/pinctrl-spmi-gpio.c static const struct of_device_id pmic_gpio_of_match[] = { · line 1136

Quoted 6 lines
drivers/pinctrl/qcom/pinctrl-spmi-gpio.c +3 -0
@@ -1131,6 +1131,10 @@ static const struct of_device_id pmic_gpio_of_match[] = {
 	{ .compatible = "qcom,pm6150l-gpio", .data = (void *) 12 },
 	/* pmx55 has 11 GPIOs with holes on 3, 7, 10, 11 */
 	{ .compatible = "qcom,pmx55-gpio", .data = (void *) 11 },
+	{ .compatible = "qcom,pm7325-gpio", .data = (void *) 10 },
+	{ .compatible = "qcom,pm8350c-gpio", .data = (void *) 9 },
+	{ .compatible = "qcom,pmk8350-gpio", .data = (void *) 4 },

Please try to keep the list sorted alphabetically, that way you'd see that linux-next already has pm8350c and pmk8350 defined - or at least Linus would notice when he tries to apply your patch.

Regards,
Bjorn

Quoted 8 lines
drivers/pinctrl/qcom/pinctrl-spmi-gpio.c +1 -0
+	{ .compatible = "qcom,pmr735a-gpio", .data = (void *) 4 },
 	{ },
 };
 
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member 
of Code Aurora Forum, hosted by The Linux Foundation
#3 lore raw

PATCH v2 2/3 dt-bindings: pinctrl: qcom-pmic-gpio: Update the binding to add four new variants

In reply to satya priya

Update the binding to add PM7325, PM8350C, PMK8350 and PMR735A GPIO support.

---
Changes in V2:
- Placed this patch before conversion patch and updated commit text to be more clear.

 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 8 ++++++++
 1 file changed, 8 insertions(+)
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt +8 -0
index 7648ab0..da7c35e 100644
@@ -30,6 +30,10 @@ PMIC's from Qualcomm.
 		    "qcom,pm6150-gpio"
 		    "qcom,pm6150l-gpio"
 		    "qcom,pmx55-gpio"
+		    "qcom,pm7325-gpio"
+		    "qcom,pm8350c-gpio"
+		    "qcom,pmk8350-gpio"
+		    "qcom,pmr735a-gpio"
 
 		    And must contain either "qcom,spmi-gpio" or "qcom,ssbi-gpio"
 		    if the device is on an spmi bus or an ssbi bus respectively
@@ -113,6 +117,10 @@ to specify in a pin configuration subnode:
 		    gpio1-gpio12 for pm6150l
 		    gpio1-gpio11 for pmx55 (holes on gpio3, gpio7, gpio10
 					    and gpio11)
+		    gpio1-gpio10 for pm7325
+		    gpio1-gpio9 for pm8350c
+		    gpio1-gpio4 for pmk8350
+		    gpio1-gpio4 for pmr735a
 
 - function:
 	Usage: required
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member 
of Code Aurora Forum, hosted by The Linux Foundation
#4 lore raw

Re: [PATCH V2 2/3] dt-bindings: pinctrl: qcom-pmic-gpio: Update the binding to add four new variants

Quoted 16 lines · satya priya

Update the binding to add PM7325, PM8350C, PMK8350 and PMR735A GPIO support.

---
Changes in V2:
- Placed this patch before conversion patch and updated commit text to be more clear.

 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 8 ++++++++
 1 file changed, 8 insertions(+)
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt +0 -0
index 7648ab0..da7c35e 100644

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt PMIC's from Qualcomm. · line 36

Quoted 7 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt +4 -0
@@ -30,6 +30,10 @@ PMIC's from Qualcomm.
 		    "qcom,pm6150-gpio"
 		    "qcom,pm6150l-gpio"
 		    "qcom,pmx55-gpio"
+		    "qcom,pm7325-gpio"
+		    "qcom,pm8350c-gpio"
+		    "qcom,pmk8350-gpio"
+		    "qcom,pmr735a-gpio"

As with the driver, please try to keep these sorted alphabetically and please rebase on linux-next, which already defines 2 of these.

Regards,
Bjorn

Quoted 18 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt +4 -0
 		    And must contain either "qcom,spmi-gpio" or "qcom,ssbi-gpio"
 		    if the device is on an spmi bus or an ssbi bus respectively
@@ -113,6 +117,10 @@ to specify in a pin configuration subnode:
 		    gpio1-gpio12 for pm6150l
 		    gpio1-gpio11 for pmx55 (holes on gpio3, gpio7, gpio10
 					    and gpio11)
+		    gpio1-gpio10 for pm7325
+		    gpio1-gpio9 for pm8350c
+		    gpio1-gpio4 for pmk8350
+		    gpio1-gpio4 for pmr735a
 
 - function:
 	Usage: required
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member 
of Code Aurora Forum, hosted by The Linux Foundation
#5 lore raw

PATCH v2 3/3 dt-bindings: pinctrl: qcom-pmic-gpio: Convert qcom pmic gpio bindings to YAML

In reply to satya priya

Convert Qualcomm PMIC GPIO bindings from .txt to .yaml format.

---
Changes in V3:
- As per Rob's comments fixed bot erros.
- Moved this patch to end of the series so that other patches are not blocked on this.

 .../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 280 --------------------
 .../bindings/pinctrl/qcom,pmic-gpio.yaml           | 281 +++++++++++++++++++++
 2 files changed, 281 insertions(+), 280 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
 create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt deleted +0 -280
deleted file mode 100644
index da7c35e..0000000
@@ -1,280 +0,0 @@
-Qualcomm PMIC GPIO block
-
-This binding describes the GPIO block(s) found in the 8xxx series of
-PMIC's from Qualcomm.
-
-- compatible:
-	Usage: required
-	Value type: <string>
-	Definition: must be one of:
-		    "qcom,pm8005-gpio"
-		    "qcom,pm8018-gpio"
-		    "qcom,pm8038-gpio"
-		    "qcom,pm8058-gpio"
-		    "qcom,pm8916-gpio"
-		    "qcom,pm8917-gpio"
-		    "qcom,pm8921-gpio"
-		    "qcom,pm8941-gpio"
-		    "qcom,pm8950-gpio"
-		    "qcom,pm8994-gpio"
-		    "qcom,pm8998-gpio"
-		    "qcom,pma8084-gpio"
-		    "qcom,pmi8950-gpio"
-		    "qcom,pmi8994-gpio"
-		    "qcom,pmi8998-gpio"
-		    "qcom,pms405-gpio"
-		    "qcom,pm660-gpio"
-		    "qcom,pm660l-gpio"
-		    "qcom,pm8150-gpio"
-		    "qcom,pm8150b-gpio"
-		    "qcom,pm6150-gpio"
-		    "qcom,pm6150l-gpio"
-		    "qcom,pmx55-gpio"
-		    "qcom,pm7325-gpio"
-		    "qcom,pm8350c-gpio"
-		    "qcom,pmk8350-gpio"
-		    "qcom,pmr735a-gpio"
-
-		    And must contain either "qcom,spmi-gpio" or "qcom,ssbi-gpio"
-		    if the device is on an spmi bus or an ssbi bus respectively
-
-- reg:
-	Usage: required
-	Value type: <prop-encoded-array>
-	Definition: Register base of the GPIO block and length.
-
-- interrupts:
-	Usage: required
-	Value type: <prop-encoded-array>
-	Definition: Must contain an array of encoded interrupt specifiers for
-		    each available GPIO
-
-- gpio-controller:
-	Usage: required
-	Value type: <none>
-	Definition: Mark the device node as a GPIO controller
-
-- #gpio-cells:
-	Usage: required
-	Value type: <u32>
-	Definition: Must be 2;
-		    the first cell will be used to define gpio number and the
-		    second denotes the flags for this gpio
-
-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 or a list of pins. This configuration can include the
-mux function to select on those pin(s), and various pin configuration
-parameters, as listed below.
-
-
-SUBNODES:
-
-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: <string-array>
-	Definition: List of gpio pins affected by the properties specified in
-		    this subnode.  Valid pins are:
-		    gpio1-gpio4 for pm8005
-		    gpio1-gpio6 for pm8018
-		    gpio1-gpio12 for pm8038
-		    gpio1-gpio40 for pm8058
-		    gpio1-gpio4 for pm8916
-		    gpio1-gpio38 for pm8917
-		    gpio1-gpio44 for pm8921
-		    gpio1-gpio36 for pm8941
-		    gpio1-gpio8 for pm8950 (hole on gpio3)
-		    gpio1-gpio22 for pm8994
-		    gpio1-gpio26 for pm8998
-		    gpio1-gpio22 for pma8084
-		    gpio1-gpio2 for pmi8950
-		    gpio1-gpio10 for pmi8994
-		    gpio1-gpio12 for pms405 (holes on gpio1, gpio9 and gpio10)
-		    gpio1-gpio10 for pm8150 (holes on gpio2, gpio5, gpio7
-					     and gpio8)
-		    gpio1-gpio12 for pm8150b (holes on gpio3, gpio4, gpio7)
-		    gpio1-gpio12 for pm8150l (hole on gpio7)
-		    gpio1-gpio10 for pm6150
-		    gpio1-gpio12 for pm6150l
-		    gpio1-gpio11 for pmx55 (holes on gpio3, gpio7, gpio10
-					    and gpio11)
-		    gpio1-gpio10 for pm7325
-		    gpio1-gpio9 for pm8350c
-		    gpio1-gpio4 for pmk8350
-		    gpio1-gpio4 for pmr735a
-
-- function:
-	Usage: required
-	Value type: <string>
-	Definition: Specify the alternative function to be configured for the
-		    specified pins.  Valid values are:
-		    "normal",
-		    "paired",
-		    "func1",
-		    "func2",
-		    "dtest1",
-		    "dtest2",
-		    "dtest3",
-		    "dtest4",
-		    And following values are supported by LV/MV GPIO subtypes:
-		    "func3",
-		    "func4"
-
-- bias-disable:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins should be configured as no pull.
-
-- bias-pull-down:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins should be configured as pull down.
-
-- bias-pull-up:
-	Usage: optional
-	Value type: <empty>
-	Definition: The specified pins should be configured as pull up.
-
-- qcom,pull-up-strength:
-	Usage: optional
-	Value type: <u32>
-	Definition: Specifies the strength to use for pull up, if selected.
-		    Valid values are; as defined in
-		    <dt-bindings/pinctrl/qcom,pmic-gpio.h>:
-		    1: 30uA                     (PMIC_GPIO_PULL_UP_30)
-		    2: 1.5uA                    (PMIC_GPIO_PULL_UP_1P5)
-		    3: 31.5uA                   (PMIC_GPIO_PULL_UP_31P5)
-		    4: 1.5uA + 30uA boost       (PMIC_GPIO_PULL_UP_1P5_30)
-		    If this property is omitted 30uA strength will be used if
-		    pull up is selected
-
-- bias-high-impedance:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins will put in high-Z mode and disabled.
-
-- input-enable:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins are put in input mode.
-
-- output-high:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins are configured in output mode, driven
-		    high.
-
-- output-low:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins are configured in output mode, driven
-		    low.
-
-- power-source:
-	Usage: optional
-	Value type: <u32>
-	Definition: Selects the power source for the specified pins. Valid
-		    power sources are defined per chip in
-		    <dt-bindings/pinctrl/qcom,pmic-gpio.h>
-
-- qcom,drive-strength:
-	Usage: optional
-	Value type: <u32>
-	Definition: Selects the drive strength for the specified pins. Value
-		    drive strengths are:
-		    0: no (PMIC_GPIO_STRENGTH_NO)
-		    1: high (PMIC_GPIO_STRENGTH_HIGH) 0.9mA @ 1.8V - 1.9mA @ 2.6V
-		    2: medium (PMIC_GPIO_STRENGTH_MED) 0.6mA @ 1.8V - 1.25mA @ 2.6V
-		    3: low (PMIC_GPIO_STRENGTH_LOW) 0.15mA @ 1.8V - 0.3mA @ 2.6V
-		    as defined in <dt-bindings/pinctrl/qcom,pmic-gpio.h>
-
-- drive-push-pull:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins are configured in push-pull mode.
-
-- drive-open-drain:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins are configured in open-drain mode.
-
-- drive-open-source:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins are configured in open-source mode.
-
-- qcom,analog-pass:
-	Usage: optional
-	Value type: <none>
-	Definition: The specified pins are configured in analog-pass-through mode.
-
-- qcom,atest:
-	Usage: optional
-	Value type: <u32>
-	Definition: Selects ATEST rail to route to GPIO when it's configured
-		    in analog-pass-through mode.
-		    Valid values are 1-4 corresponding to ATEST1 to ATEST4.
-
-- qcom,dtest-buffer:
-	Usage: optional
-	Value type: <u32>
-	Definition: Selects DTEST rail to route to GPIO when it's configured
-		    as digital input.
-		    Valid values are 1-4 corresponding to DTEST1 to DTEST4.
-
-Example:
-
-	pm8921_gpio: gpio@150 {
-		compatible = "qcom,pm8921-gpio", "qcom,ssbi-gpio";
-		reg = <0x150 0x160>;
-		interrupts = <192 1>, <193 1>, <194 1>,
-			     <195 1>, <196 1>, <197 1>,
-			     <198 1>, <199 1>, <200 1>,
-			     <201 1>, <202 1>, <203 1>,
-			     <204 1>, <205 1>, <206 1>,
-			     <207 1>, <208 1>, <209 1>,
-			     <210 1>, <211 1>, <212 1>,
-			     <213 1>, <214 1>, <215 1>,
-			     <216 1>, <217 1>, <218 1>,
-			     <219 1>, <220 1>, <221 1>,
-			     <222 1>, <223 1>, <224 1>,
-			     <225 1>, <226 1>, <227 1>,
-			     <228 1>, <229 1>, <230 1>,
-			     <231 1>, <232 1>, <233 1>,
-			     <234 1>, <235 1>;
-
-		gpio-controller;
-		#gpio-cells = <2>;
-
-		pm8921_gpio_keys: gpio-keys {
-			volume-keys {
-				pins = "gpio20", "gpio21";
-				function = "normal";
-
-				input-enable;
-				bias-pull-up;
-				drive-push-pull;
-				qcom,drive-strength = <PMIC_GPIO_STRENGTH_NO>;
-				power-source = <PM8921_GPIO_S4>;
-			};
-		};
-	};
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +281 -0

281 lines not on this page · raw message

Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member 
of Code Aurora Forum, hosted by The Linux Foundation
maintainer
#6 lore raw

Re: [PATCH V2 3/3] dt-bindings: pinctrl: qcom-pmic-gpio: Convert qcom pmic gpio bindings to YAML

Quoted 62 lines · satya priya

Convert Qualcomm PMIC GPIO bindings from .txt to .yaml format.

---
Changes in V3:
- As per Rob's comments fixed bot erros.
- Moved this patch to end of the series so that other patches are not blocked on this.

 .../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 280 --------------------
 .../bindings/pinctrl/qcom,pmic-gpio.yaml           | 281 +++++++++++++++++++++
 2 files changed, 281 insertions(+), 280 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
 create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +40 -0
new file mode 100644
index 0000000..e7e7027
@@ -0,0 +1,281 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/pinctrl/qcom,pmic-gpio.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Qualcomm PMIC GPIO block
+
+maintainers:
+  - Bjorn Andersson <[email protected]>
+
+description: |
+  This binding describes the GPIO block(s) found in the 8xxx series of
+  PMIC's from Qualcomm.
+
+properties:
+  compatible:
+    items:
+      - enum:
+          - qcom,pm8005-gpio
+          - qcom,pm8018-gpio
+          - qcom,pm8038-gpio
+          - qcom,pm8058-gpio
+          - qcom,pm8916-gpio
+          - qcom,pm8917-gpio
+          - qcom,pm8921-gpio
+          - qcom,pm8941-gpio
+          - qcom,pm8950-gpio
+          - qcom,pm8994-gpio
+          - qcom,pm8998-gpio
+          - qcom,pma8084-gpio
+          - qcom,pmi8950-gpio
+          - qcom,pmi8994-gpio
+          - qcom,pmi8998-gpio
+          - qcom,pms405-gpio
+          - qcom,pm660-gpio
+          - qcom,pm660l-gpio
+          - qcom,pm8150-gpio
+          - qcom,pm8150b-gpio
+          - qcom,pm6150-gpio

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 50

Quoted 10 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +10 -0
+          - qcom,pm6150l-gpio
+          - qcom,pmx55-gpio
+          - qcom,pm7325-gpio
+          - qcom,pm8350c-gpio
+          - qcom,pmk8350-gpio
+          - qcom,pmr735a-gpio
+
+      - enum:
+          - qcom,spmi-gpio
+          - qcom,ssbi-gpio

Any combination of the 1st and 2nd entry is valid?

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 53

Quoted 3 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +3 -0
+
+  reg:
+    description: Register base of the GPIO block and length.

Just:

maxItems: 1

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 58

Quoted 5 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +5 -0
+
+  interrupts:
+    description: |
+        Must contain an array of encoded interrupt specifiers for
+        each available GPIO

Need to define how many interrupts. I assume there's some max.

Quoted 12 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +12 -0
+
+  '#interrupt-cells':
+    const: 2
+
+  interrupt-controller: true
+
+  gpio-controller: true
+
+  gpio-ranges:
+    maxItems: 1
+
+  '#gpio-cells':

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 80

Quoted 10 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +10 -0
+    const: 2
+    description: |
+        The first cell will be used to define gpio number and the
+        second denotes the flags for this gpio
+
+  gpio-keys:
+    type: object
+    properties:
+      volume-keys:
+        type: object

Needs a $ref to pinmux-node.yaml and pincfg-node.yaml.

Quoted 24 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +24 -0
+        properties:
+          pins:
+            description: |
+                List of gpio pins affected by the properties specified in
+                this subnode.  Valid pins are
+                     - gpio1-gpio4 for pm8005
+                     - gpio1-gpio6 for pm8018
+                     - gpio1-gpio12 for pm8038
+                     - gpio1-gpio40 for pm8058
+                     - gpio1-gpio4 for pm8916
+                     - gpio1-gpio38 for pm8917
+                     - gpio1-gpio44 for pm8921
+                     - gpio1-gpio36 for pm8941
+                     - gpio1-gpio8 for pm8950 (hole on gpio3)
+                     - gpio1-gpio22 for pm8994
+                     - gpio1-gpio26 for pm8998
+                     - gpio1-gpio22 for pma8084
+                     - gpio1-gpio2 for pmi8950
+                     - gpio1-gpio10 for pmi8994
+                     - gpio1-gpio12 for pms405 (holes on gpio1, gpio9
+                                                and gpio10)
+                     - gpio1-gpio10 for pm8150 (holes on gpio2, gpio5,
+                                                gpio7 and gpio8)
+                     - gpio1-gpio12 for pm8150b (holes on gpio3, gpio4

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 114

Quoted 10 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +10 -0
+                                                 and gpio7)
+                     - gpio1-gpio12 for pm8150l (hole on gpio7)
+                     - gpio1-gpio10 for pm6150
+                     - gpio1-gpio12 for pm6150l
+                     - gpio1-gpio10 for pm7325
+                     - gpio1-gpio9 for pm8350c
+                     - gpio1-gpio4 for pmk8350
+                     - gpio1-gpio4 for pmr735a
+
+            $ref: /schemas/types.yaml#/definitions/string-array

Already has a type in pinmux-node.yaml.

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 119

Quoted 5 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +5 -0
+            items:
+              pattern: "^gpio([0-9]+)$"
+
+          function:
+            $ref: /schemas/types.yaml#/definitions/string

ditto

Quoted 8 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +8 -0
+            description: |
+                Specify the alternative function to be configured for the
+                specified pins.
+            items:
+              - enum:
+                  - normal
+                  - paired
+                  - func1

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 137

Quoted 10 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +10 -0
+                  - func2
+                  - dtest1
+                  - dtest2
+                  - dtest3
+                  - dtest4
+                  - func3  # supported by LV/MV GPIO subtypes
+                  - func4  # supported by LV/MV GPIO subtypes
+
+          bias-disable:
+            $ref: /schemas/types.yaml#/definitions/flag

And all these have a type and description. Just:

bias-disable: true

If no further constraints.

Quoted 89 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +89 -0
+            description:
+              The specified pins should be configured as no pull.
+
+          bias-pull-down:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description:
+              The specified pins should be configured as pull down.
+
+          bias-pull-up:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description:
+              The specified pins should be configured as pull up.
+
+          qcom,pull-up-strength:
+            $ref: /schemas/types.yaml#/definitions/uint32
+            description: |
+                Specifies the strength to use for pull up, if selected.
+                Valid values are defined in
+                <dt-bindings/pinctrl/qcom,pmic-gpio.h>
+                If this property is omitted 30uA strength will be used
+                if pull up is selected
+
+          bias-high-impedance:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description:
+              The specified pins will put in high-Z mode and disabled.
+
+          input-enable:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description: The specified pins are put in input mode.
+
+          output-high:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description: |
+                The specified pins are configured in output mode,
+                driven high.
+
+          output-low:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description: |
+                The specified pins are configured in output mode,
+                driven low.
+
+          power-source:
+            $ref: /schemas/types.yaml#/definitions/uint32
+            description: |
+                Selects the power source for the specified pins.
+                Valid power sources are defined per chip in
+                <dt-bindings/pinctrl/qcom,pmic-gpio.h>
+
+          qcom,drive-strength:
+            $ref: /schemas/types.yaml#/definitions/uint32
+            description: |
+                Selects the drive strength for the specified pins
+                Valid drive strength values are defined in
+                <dt-bindings/pinctrl/qcom,pmic-gpio.h>
+
+          drive-push-pull:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description:
+              The specified pins are configured in push-pull mode.
+
+          drive-open-drain:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description:
+              The specified pins are configured in open-drain mode.
+
+          drive-open-source:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description:
+              The specified pins are configured in open-source mode.
+
+          qcom,analog-pass:
+            $ref: /schemas/types.yaml#/definitions/flag
+            description: |
+                The specified pins are configured in
+                analog-pass-through mode.
+
+          qcom,atest:
+            $ref: /schemas/types.yaml#/definitions/uint32
+            description: |
+                Selects ATEST rail to route to GPIO when it's
+                configured in analog-pass-through mode.
+            enum: [1 2 3 4]
+
+          qcom,dtest-buffer:
+            $ref: /schemas/types.yaml#/definitions/uint32
+            description: |
+                Selects DTEST rail to route to GPIO when it's

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 236

Quoted 10 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +10 -0
+                configured as digital input.
+            enum: [1 2 3 4]
+
+        required:
+          - pins
+          - function
+
+        additionalProperties: true
+
+additionalProperties: true

Should be 'false'.

Quoted 49 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +45 -0
+
+required:
+  - compatible
+  - reg
+
+examples:
+  - |
+    #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
+
+    pm8921_gpio: gpio@150 {
+      compatible = "qcom,pm8921-gpio", "qcom,ssbi-gpio";
+      reg = <0x150 0x160>;
+      interrupts = <192 1>, <193 1>, <194 1>,
+                   <195 1>, <196 1>, <197 1>,
+                   <198 1>, <199 1>, <200 1>,
+                   <201 1>, <202 1>, <203 1>,
+                   <204 1>, <205 1>, <206 1>,
+                   <207 1>, <208 1>, <209 1>,
+                   <210 1>, <211 1>, <212 1>,
+                   <213 1>, <214 1>, <215 1>,
+                   <216 1>, <217 1>, <218 1>,
+                   <219 1>, <220 1>, <221 1>,
+                   <222 1>, <223 1>, <224 1>,
+                   <225 1>, <226 1>, <227 1>,
+                   <228 1>, <229 1>, <230 1>,
+                   <231 1>, <232 1>, <233 1>,
+                   <234 1>, <235 1>;
+
+      gpio-controller;
+      #gpio-cells = <2>;
+
+      pm8921_gpio_keys: gpio-keys {
+        volume-keys {
+          pins = "gpio20", "gpio21";
+          function = "normal";
+
+          input-enable;
+          bias-pull-up;
+          drive-push-pull;
+          qcom,drive-strength = <PMIC_GPIO_STRENGTH_NO>;
+          power-source = <PM8921_GPIO_S4>;
+        };
+      };
+    };
+...
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member 
of Code Aurora Forum, hosted by The Linux Foundation
#7 lore raw

Re: [PATCH V2 3/3] dt-bindings: pinctrl: qcom-pmic-gpio: Convert qcom pmic gpio bindings to YAML

Hi Rob,

Quoted 72 lines · Rob Herring
Quoted 71 lines · satya priya

Convert Qualcomm PMIC GPIO bindings from .txt to .yaml format.

---
Changes in V3:
- As per Rob's comments fixed bot erros.
- Moved this patch to end of the series so that other patches are not blocked on this.

 .../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 280 
--------------------
 .../bindings/pinctrl/qcom,pmic-gpio.yaml           | 281 
+++++++++++++++++++++
 2 files changed, 281 insertions(+), 280 deletions(-)
 delete mode 100644 
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt
 create mode 100644 

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +13 -0
new file mode 100644
index 0000000..e7e7027
@@ -0,0 +1,281 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/pinctrl/qcom,pmic-gpio.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Qualcomm PMIC GPIO block
+
+maintainers:
+  - Bjorn Andersson <[email protected]>
+
+description: |
+  This binding describes the GPIO block(s) found in the 8xxx series 

of

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +31 -0
+  PMIC's from Qualcomm.
+
+properties:
+  compatible:
+    items:
+      - enum:
+          - qcom,pm8005-gpio
+          - qcom,pm8018-gpio
+          - qcom,pm8038-gpio
+          - qcom,pm8058-gpio
+          - qcom,pm8916-gpio
+          - qcom,pm8917-gpio
+          - qcom,pm8921-gpio
+          - qcom,pm8941-gpio
+          - qcom,pm8950-gpio
+          - qcom,pm8994-gpio
+          - qcom,pm8998-gpio
+          - qcom,pma8084-gpio
+          - qcom,pmi8950-gpio
+          - qcom,pmi8994-gpio
+          - qcom,pmi8998-gpio
+          - qcom,pms405-gpio
+          - qcom,pm660-gpio
+          - qcom,pm660l-gpio
+          - qcom,pm8150-gpio
+          - qcom,pm8150b-gpio
+          - qcom,pm6150-gpio
+          - qcom,pm6150l-gpio
+          - qcom,pmx55-gpio
+          - qcom,pm7325-gpio
+          - qcom,pm8350c-gpio
Quoted 9 lines

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 50

Quoted 6 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +6 -0
+          - qcom,pmk8350-gpio
+          - qcom,pmr735a-gpio
+
+      - enum:
+          - qcom,spmi-gpio
+          - qcom,ssbi-gpio

Any combination of the 1st and 2nd entry is valid?

No, for pmics which use spmi and ssbi buses, "qcom,spmi-gpio" and "qcom,ssbi-gpio" compatibles should be used respectively.

Quoted 8 lines

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 53

Quoted 3 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +3 -0
+
+  reg:
+    description: Register base of the GPIO block and length.

Just:

maxItems: 1

ok.

Quoted 8 lines

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 58

Quoted 5 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +5 -0
+
+  interrupts:
+    description: |
+        Must contain an array of encoded interrupt specifiers for
+        each available GPIO

Need to define how many interrupts. I assume there's some max.

ok will add maxItems.

Quoted 16 lines
Quoted 16 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +16 -0
+
+  '#interrupt-cells':
+    const: 2
+
+  interrupt-controller: true
+
+  gpio-controller: true
+
+  gpio-ranges:
+    maxItems: 1
+
+  '#gpio-cells':
+    const: 2
+    description: |
+        The first cell will be used to define gpio number and the
+        second denotes the flags for this gpio
Quoted 9 lines

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 80

Quoted 6 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +6 -0
+
+  gpio-keys:
+    type: object
+    properties:
+      volume-keys:
+        type: object

Needs a $ref to pinmux-node.yaml and pincfg-node.yaml.

can I add like below?

volume-keys:
type: object
+ anyOf:
+ - $ref: "pinmux-node.yaml"
+ - $ref: "pincfg-node.yaml"

Quoted 38 lines
Quoted 27 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +4 -0
+        properties:
+          pins:
+            description: |
+                List of gpio pins affected by the properties 

specified in

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +18 -0
+                this subnode.  Valid pins are
+                     - gpio1-gpio4 for pm8005
+                     - gpio1-gpio6 for pm8018
+                     - gpio1-gpio12 for pm8038
+                     - gpio1-gpio40 for pm8058
+                     - gpio1-gpio4 for pm8916
+                     - gpio1-gpio38 for pm8917
+                     - gpio1-gpio44 for pm8921
+                     - gpio1-gpio36 for pm8941
+                     - gpio1-gpio8 for pm8950 (hole on gpio3)
+                     - gpio1-gpio22 for pm8994
+                     - gpio1-gpio26 for pm8998
+                     - gpio1-gpio22 for pma8084
+                     - gpio1-gpio2 for pmi8950
+                     - gpio1-gpio10 for pmi8994
+                     - gpio1-gpio12 for pms405 (holes on gpio1, gpio9
+                                                and gpio10)
+                     - gpio1-gpio10 for pm8150 (holes on gpio2, 

gpio5,

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +2 -0
+                                                gpio7 and gpio8)
+                     - gpio1-gpio12 for pm8150b (holes on gpio3, 

gpio4

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 114

Quoted 10 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +10 -0
+                                                 and gpio7)
+                     - gpio1-gpio12 for pm8150l (hole on gpio7)
+                     - gpio1-gpio10 for pm6150
+                     - gpio1-gpio12 for pm6150l
+                     - gpio1-gpio10 for pm7325
+                     - gpio1-gpio9 for pm8350c
+                     - gpio1-gpio4 for pmk8350
+                     - gpio1-gpio4 for pmr735a
+
+            $ref: /schemas/types.yaml#/definitions/string-array
Quoted 2 lines

Already has a type in pinmux-node.yaml.

Okay, will add above and remove here.

Quoted 8 lines

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 119

Quoted 5 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +5 -0
+            items:
+              pattern: "^gpio([0-9]+)$"
+
+          function:
+            $ref: /schemas/types.yaml#/definitions/string

ditto

Okay, will add above and remove here.

Quoted 20 lines
Quoted 9 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +2 -0
+            description: |
+                Specify the alternative function to be configured for 

the

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +6 -0
+                specified pins.
+            items:
+              - enum:
+                  - normal
+                  - paired
+                  - func1

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 137

Quoted 10 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +10 -0
+                  - func2
+                  - dtest1
+                  - dtest2
+                  - dtest3
+                  - dtest4
+                  - func3  # supported by LV/MV GPIO subtypes
+                  - func4  # supported by LV/MV GPIO subtypes
+
+          bias-disable:
+            $ref: /schemas/types.yaml#/definitions/flag
Quoted 6 lines

And all these have a type and description. Just:

bias-disable: true

If no further constraints.

Okay.

Quoted 5 lines
Quoted 5 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +5 -0
+            description:
+              The specified pins should be configured as no pull.
+
+          bias-pull-down:
+            $ref: /schemas/types.yaml#/definitions/flag

[...]

Quoted 6 lines

Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml line 236

Quoted 3 lines
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml new file +3 -0
+        additionalProperties: true
+
+additionalProperties: true

Should be 'false'.

Okay.

Thanks,
Satya Priya

#8 lore raw
In reply to satya priya
Quoted 6 lines · satya priya

satya priya (3):
pinctrl: qcom: spmi-gpio: Add support for four variants
dt-bindings: pinctrl: qcom-pmic-gpio: Update the binding to add four
new variants
dt-bindings: pinctrl: qcom-pmic-gpio: Convert qcom pmic gpio bindings
to YAML

Please collect the ACKs and rebase like Björn says, sort stuff alphabetically and resend so I can try to apply it! The YAML conversion may need a nod from the DT people as well.

Yours,
Linus Walleij

#9 lore raw
Quoted 10 lines · Linus Walleij
Quoted 7 lines · satya priya

satya priya (3):
pinctrl: qcom: spmi-gpio: Add support for four variants
dt-bindings: pinctrl: qcom-pmic-gpio: Update the binding to add four
new variants
dt-bindings: pinctrl: qcom-pmic-gpio: Convert qcom pmic gpio
bindings
to YAML

Quoted 4 lines

Please collect the ACKs and rebase like Björn says, sort stuff alphabetically and resend so I can try to apply it! The YAML conversion may need a nod from the DT people as well.

Sure, will address the comments and resend.

Quoted 2 lines

Yours,
Linus Walleij

Thanks,
Satya Priya