All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Tony Lindgren <tony@atomide.com>, <devicetree@vger.kernel.org>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-omap@vger.kernel.org>,
	Aswath Govindraju <a-govindraju@ti.com>,
	Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [PATCH v2 0/5] dt-bindings: gpio: omap: Convert to json-schema
Date: Tue, 25 May 2021 20:58:53 +0300	[thread overview]
Message-ID: <20210525175858.11611-1-grygorii.strashko@ti.com> (raw)

Hi

Convert the OMAP GPIO Device Tree binding documentation to json-schema.
The GPIO hogs node names defined to end with a 'hog' suffix.

All existing GPIO Hogs fixed to follow above naming convention
before changing the binding to avoid dtbs_check warnings.

Changes in v2:
- Patch 5 fixed "wrong indentation" warning

v1: https://lore.kernel.org/patchwork/cover/1434566/

Grygorii Strashko (5):
  ARM: dts: am335x: align GPIO hog names with dt-schema
  ARM: dts: am437x: align gpio hog names with dt-schema
  ARM: dts: omap3: align gpio hog names with dt-schema
  ARM: dts: omap5-board-common: align gpio hog names with dt-schema
  dt-bindings: gpio: omap: Convert to json-schema

 .../devicetree/bindings/gpio/gpio-omap.txt    |  45 --------
 .../bindings/gpio/ti,omap-gpio.yaml           | 108 ++++++++++++++++++
 .../boot/dts/am335x-boneblack-wireless.dts    |   2 +-
 arch/arm/boot/dts/am335x-boneblue.dts         |   2 +-
 .../boot/dts/am335x-bonegreen-wireless.dts    |   4 +-
 arch/arm/boot/dts/am335x-icev2.dts            |   4 +-
 arch/arm/boot/dts/am335x-shc.dts              |   8 +-
 arch/arm/boot/dts/am437x-gp-evm.dts           |   4 +-
 arch/arm/boot/dts/am43x-epos-evm.dts          |   2 +-
 .../boot/dts/omap3-evm-processor-common.dtsi  |   2 +-
 arch/arm/boot/dts/omap3-gta04a5.dts           |   2 +-
 arch/arm/boot/dts/omap5-board-common.dtsi     |   2 +-
 12 files changed, 124 insertions(+), 61 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/gpio/gpio-omap.txt
 create mode 100644 Documentation/devicetree/bindings/gpio/ti,omap-gpio.yaml

-- 
2.17.1


             reply	other threads:[~2021-05-25 17:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 17:58 Grygorii Strashko [this message]
2021-05-25 17:58 ` [PATCH v2 1/5] ARM: dts: am335x: align GPIO hog names with dt-schema Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 2/5] ARM: dts: am437x: align gpio " Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 3/5] ARM: dts: omap3: " Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 4/5] ARM: dts: omap5-board-common: " Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 5/5] dt-bindings: gpio: omap: Convert to json-schema Grygorii Strashko
2021-05-26 11:28   ` Bartosz Golaszewski
2021-05-26 10:06 ` [PATCH v2 0/5] " Grygorii Strashko
2021-05-27 12:01   ` Tony Lindgren

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=20210525175858.11611-1-grygorii.strashko@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=a-govindraju@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.