From: Rob Herring <robh@kernel•org>
To: Benjamin Gaignard <benjamin.gaignard@st•com>
Cc: mark.rutland@arm•com, devicetree@vger•kernel.org,
lars@metafoo•de, alexandre.torgue@st•com,
linux-pwm@vger•kernel.org, linux-iio@vger•kernel.org,
u.kleine-koenig@pengutronix•de, linux-kernel@vger•kernel.org,
robh+dt@kernel•org, thierry.reding@gmail•com,
linux-arm-kernel@lists•infradead.org, pmeerw@pmeerw•net,
knaack.h@gmx•de, fabrice.gasnier@st•com, lee.jones@linaro•org,
linux-stm32@st-md-mailman•stormreply.com, jic23@kernel•org,
benjamin.gaignard@st•com
Subject: Re: [PATCH v3] dt-bindings: mfd: Convert stm32 timers bindings to json-schema
Date: Thu, 14 Nov 2019 11:31:29 -0600 [thread overview]
Message-ID: <20191114173129.GA25237@bogus> (raw)
In-Reply-To: <20191114101823.23144-1-benjamin.gaignard@st.com>
On Thu, 14 Nov 2019 11:18:23 +0100, Benjamin Gaignard wrote:
> Convert the STM32 timers binding to DT schema format using json-schema
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st•com>
> ---
> version 3:
> - correctly use enum for dma-names and remove additionalItems: true
> - provide a range of values for reg property
>
> version 2:
> - merge all (mfd, iio, pwm, counter) bindings in one file
> - fix typo and trailing spaces
> - rework dmas and dma-names properties to allow schemas like:
> ch1 , ch2, ch4
> ch2, up, com
> - use patternProperties to describe timer subnode
> - improve st,breakinput property definition to be able to check the values
> inside de tuple
>
> .../bindings/counter/stm32-timer-cnt.txt | 31 ----
> .../bindings/iio/timer/stm32-timer-trigger.txt | 25 ----
> .../devicetree/bindings/mfd/st,stm32-timers.yaml | 159 +++++++++++++++++++++
> .../devicetree/bindings/mfd/stm32-timers.txt | 73 ----------
> .../devicetree/bindings/pwm/pwm-stm32.txt | 38 -----
> 5 files changed, 159 insertions(+), 167 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/counter/stm32-timer-cnt.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt
> create mode 100644 Documentation/devicetree/bindings/mfd/st,stm32-timers.yaml
> delete mode 100644 Documentation/devicetree/bindings/mfd/stm32-timers.txt
> delete mode 100644 Documentation/devicetree/bindings/pwm/pwm-stm32.txt
>
Applied, thanks.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-14 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 10:18 [PATCH v3] dt-bindings: mfd: Convert stm32 timers bindings to json-schema Benjamin Gaignard
2019-11-14 17:31 ` Rob Herring [this message]
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=20191114173129.GA25237@bogus \
--to=robh@kernel$(echo .)org \
--cc=alexandre.torgue@st$(echo .)com \
--cc=benjamin.gaignard@st$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=fabrice.gasnier@st$(echo .)com \
--cc=jic23@kernel$(echo .)org \
--cc=knaack.h@gmx$(echo .)de \
--cc=lars@metafoo$(echo .)de \
--cc=lee.jones@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-iio@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-pwm@vger$(echo .)kernel.org \
--cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
--cc=mark.rutland@arm$(echo .)com \
--cc=pmeerw@pmeerw$(echo .)net \
--cc=robh+dt@kernel$(echo .)org \
--cc=thierry.reding@gmail$(echo .)com \
--cc=u.kleine-koenig@pengutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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