From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Lee Jones <lee.jones@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
linux-pm@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH v3 0/6] dt-bindings: max77650: convert the device-tree bindings to yaml
Date: Thu, 17 Oct 2019 09:12:28 +0200 [thread overview]
Message-ID: <20191017071234.8719-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
This series converts all DT binding documents for MAX77650 PMIC to YAML.
v1 -> v2:
- use upper case for abbreviations in commit messages
v2 -> v3:
- pull all example fragments into the binding document for the core MFD module
- fix all dt_binding_check errors
- add references to submodules to the main binding document
- drop the type for gpio-line-names
- drop the description for the interrupts property
- completely delete the previous txt files
Bartosz Golaszewski (6):
dt-bindings: mfd: max77650: convert the binding document to yaml
dt-bindings: input: max77650: convert the binding document to yaml
dt-bindings: regulator: max77650: convert the binding document to yaml
dt-bindings: power: max77650: convert the binding document to yaml
dt-bindings: leds: max77650: convert the binding document to yaml
MAINTAINERS: update the list of maintained files for max77650
.../bindings/input/max77650-onkey.txt | 26 ---
.../bindings/input/max77650-onkey.yaml | 35 ++++
.../bindings/leds/leds-max77650.txt | 57 -------
.../bindings/leds/leds-max77650.yaml | 58 +++++++
.../devicetree/bindings/mfd/max77650.txt | 46 ------
.../devicetree/bindings/mfd/max77650.yaml | 151 ++++++++++++++++++
.../power/supply/max77650-charger.txt | 28 ----
.../power/supply/max77650-charger.yaml | 34 ++++
.../bindings/regulator/max77650-regulator.txt | 41 -----
.../regulator/max77650-regulator.yaml | 31 ++++
MAINTAINERS | 4 +-
11 files changed, 311 insertions(+), 200 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/input/max77650-onkey.txt
create mode 100644 Documentation/devicetree/bindings/input/max77650-onkey.yaml
delete mode 100644 Documentation/devicetree/bindings/leds/leds-max77650.txt
create mode 100644 Documentation/devicetree/bindings/leds/leds-max77650.yaml
delete mode 100644 Documentation/devicetree/bindings/mfd/max77650.txt
create mode 100644 Documentation/devicetree/bindings/mfd/max77650.yaml
delete mode 100644 Documentation/devicetree/bindings/power/supply/max77650-charger.txt
create mode 100644 Documentation/devicetree/bindings/power/supply/max77650-charger.yaml
delete mode 100644 Documentation/devicetree/bindings/regulator/max77650-regulator.txt
create mode 100644 Documentation/devicetree/bindings/regulator/max77650-regulator.yaml
--
2.23.0
next reply other threads:[~2019-10-17 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 7:12 Bartosz Golaszewski [this message]
2019-10-17 7:12 ` [PATCH v3 1/6] dt-bindings: mfd: max77650: convert the binding document to yaml Bartosz Golaszewski
2019-10-17 18:31 ` Rob Herring
2019-10-18 6:44 ` Bartosz Golaszewski
2019-10-17 7:12 ` [PATCH v3 2/6] dt-bindings: input: " Bartosz Golaszewski
2019-10-17 18:34 ` Rob Herring
2019-10-17 7:12 ` [PATCH v3 3/6] dt-bindings: regulator: " Bartosz Golaszewski
2019-10-17 18:35 ` Rob Herring
2019-10-18 6:44 ` Bartosz Golaszewski
2019-10-18 19:08 ` Rob Herring
2019-10-17 7:12 ` [PATCH v3 4/6] dt-bindings: power: " Bartosz Golaszewski
2019-10-17 7:12 ` [PATCH v3 5/6] dt-bindings: leds: " Bartosz Golaszewski
2019-10-17 18:51 ` Rob Herring
2019-10-17 7:12 ` [PATCH v3 6/6] MAINTAINERS: update the list of maintained files for max77650 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=20191017071234.8719-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
/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.