From: Aswath Govindraju <a-govindraju@ti.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Aswath Govindraju <a-govindraju@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Keerthy <j-keerthy@ti.com>,
David Lechner <david@lechnology.com>,
Sekhar Nori <nsekhar@ti.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v3 0/2] dt-bindings: gpio: davinci: Convert to json-schema
Date: Mon, 24 May 2021 20:49:52 +0530 [thread overview]
Message-ID: <20210524151955.8008-1-a-govindraju@ti.com> (raw)
Convert the davinci GPIO device tree binding documentation to json-schema.
The GPIO hog node names are defined to end with a 'hog' suffix.
All existing GPIO hogs are fixed to follow above naming convention
before changing the binding to avoid dtbs_check warnings.
changes since v2:
- Used gpio-hog.yaml for gpio-hog property
- Added constraints on gpio-hog node name
- Corrected the gpio hog dt node names to align
with the dt-schema
changes since v1:
- combined the individual compatible properties into one enum
- added maxItems and minItems properties for gpio-line-names and
interrupts
- updated the description of interrupts property
- removed the description for properties that are general
- updated the pattern property for gpio hog to indicate any sort
node name based on its usage
- corrected the example wakeup gpio node name
Aswath Govindraju (2):
ARM: dts: da850-lego-ev3: align GPIO hog names with dt-schema
dt-bindings: gpio: gpio-davinci: Convert to json-schema
.../devicetree/bindings/gpio/gpio-davinci.txt | 167 ----------------
.../bindings/gpio/gpio-davinci.yaml | 186 ++++++++++++++++++
MAINTAINERS | 2 +-
arch/arm/boot/dts/da850-lego-ev3.dts | 10 +-
4 files changed, 192 insertions(+), 173 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/gpio/gpio-davinci.txt
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-davinci.yaml
--
2.17.1
next reply other threads:[~2021-05-24 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 15:19 Aswath Govindraju [this message]
2021-05-24 15:19 ` [PATCH v3 1/2] ARM: dts: da850-lego-ev3: align GPIO hog names with dt-schema Aswath Govindraju
2021-05-24 15:52 ` David Lechner
2021-05-24 15:19 ` [PATCH v3 2/2] dt-bindings: gpio: gpio-davinci: Convert to json-schema Aswath Govindraju
2021-06-02 19:05 ` Rob Herring
2021-06-21 10:16 ` Bartosz Golaszewski
2021-06-20 7:29 ` [PATCH v3 0/2] dt-bindings: gpio: davinci: " Aswath Govindraju
2021-06-21 11:48 ` 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=20210524151955.8008-1-a-govindraju@ti.com \
--to=a-govindraju@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=kishon@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--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).