devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "M, Aparna" <a-m1@ti.com>
To: "bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"Govindraju, Aswath" <a-govindraju@ti.com>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"Raghavendra, Vignesh" <vigneshr@ti.com>,
	"Strashko, Grygorii" <grygorii.strashko@ti.com>
Subject: RE: [PATCH RESEND] dt-bindings: gpio: Convert TI TPIC2810 GPIO Controller bindings to yaml
Date: Wed, 22 Sep 2021 20:10:37 +0000	[thread overview]
Message-ID: <90c368f366e440a58928e222e1683139@ti.com> (raw)
In-Reply-To: <20210922120631.21948-1-a-m1@ti.com>

Hi Bart,

This is the latest patch resend. I'm not sure why patchwork has not been able to pick it up.


Regards,
Aparna

-----Original Message-----
From: M, Aparna 
Sent: Wednesday, September 22, 2021 5:37 PM
To: Govindraju, Aswath <a-govindraju@ti.com>; linus.walleij@linaro.org; robh+dt@kernel.org; Raghavendra, Vignesh <vigneshr@ti.com>; Strashko, Grygorii <grygorii.strashko@ti.com>
Cc: devicetree@vger.kernel.org; linux-gpio@vger.kernel.org; bgolaszewski@baylibre.com; M, Aparna <a-m1@ti.com>
Subject: [PATCH RESEND] dt-bindings: gpio: Convert TI TPIC2810 GPIO Controller bindings to yaml

* Convert gpio-tpic2810 bindings to yaml format
* Remove outdated gpio-tpic2810 bindings in .txt format

Signed-off-by: Aparna M <a-m1@ti.com>
---
 .../bindings/gpio/gpio-tpic2810.txt           | 16 --------
 .../bindings/gpio/gpio-tpic2810.yaml          | 41 +++++++++++++++++++
 2 files changed, 41 insertions(+), 16 deletions(-)  delete mode 100644 Documentation/devicetree/bindings/gpio/gpio-tpic2810.txt
 create mode 100644 Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml

diff --git a/Documentation/devicetree/bindings/gpio/gpio-tpic2810.txt b/Documentation/devicetree/bindings/gpio/gpio-tpic2810.txt
deleted file mode 100644
index 1afc2de7a537..000000000000
--- a/Documentation/devicetree/bindings/gpio/gpio-tpic2810.txt
+++ /dev/null
@@ -1,16 +0,0 @@
-TPIC2810 GPIO controller bindings
-
-Required properties:
- - compatible		: Should be "ti,tpic2810".
- - reg			: The I2C address of the device
- - gpio-controller	: Marks the device node as a GPIO controller.
- - #gpio-cells		: Should be two. For consumer use see gpio.txt.
-
-Example:
-
-	gpio@60 {
-		compatible = "ti,tpic2810";
-		reg = <0x60>;
-		gpio-controller;
-		#gpio-cells = <2>;
-	};
diff --git a/Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml b/Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml
new file mode 100644
index 000000000000..64f475eb4278
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml
@@ -0,0 +1,41 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2
+---
+$id: http://devicetree.org/schemas/gpio/gpio-tpic2810.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: TPIC2810 GPIO controller bindings
+
+maintainers:
+   - Aswath Govindraju <a-govindraju@ti.com>
+
+properties:
+  compatible:
+    enum:
+      - ti,tpic2810
+
+  reg:
+    maxItems: 1
+    description: The I2C address of the device
+
+  gpio-controller: true
+
+  "#gpio-cells":
+    const: 2
+
+required:
+    - compatible
+    - reg
+    - gpio-controller
+    - "#gpio-cells"
+
+additionalProperties: false
+
+examples:
+  - |
+    gpio1: gpio@60 {
+        compatible = "ti,tpic2810";
+        reg = <0x60>;
+        gpio-controller;
+        #gpio-cells = <2>;
+    };
--
2.17.1


       reply	other threads:[~2021-09-22 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210922120631.21948-1-a-m1@ti.com>
2021-09-22 20:10 ` M, Aparna [this message]
     [not found] <20210906083020.6038-1-a-m1@ti.com>
2021-09-08 14:27 ` [PATCH RESEND] dt-bindings: gpio: Convert TI TPIC2810 GPIO Controller bindings to yaml Grygorii Strashko
2021-09-22 10:06   ` Bartosz Golaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=90c368f366e440a58928e222e1683139@ti.com \
    --to=a-m1@ti.com \
    --cc=a-govindraju@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).