From: Benjamin Gaignard <benjamin.gaignard@st.com>
To: <gregkh@linuxfoundation.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <mcoquelin.stm32@gmail.com>,
<alexandre.torgue@st.com>
Cc: <linux-serial@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>, <fabrice.gasnier@st.com>,
<erwan.leray@st.com>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH v2 0/2] Convert STM32 UART bindings to yaml
Date: Wed, 22 Jan 2020 10:55:56 +0100 [thread overview]
Message-ID: <20200122095558.22553-1-benjamin.gaignard@st.com> (raw)
The goal of this series is to convert STM32 UART bindings to json-schema.
Since STM32 UART bindings use rs485 bindings it is also the opportunity
to convert them to json-schema.
version 2:
- remove types inside rs485-rts-delay property and add a maximum for delay
values
Benjamin Gaignard (2):
dt-bindings: serial: Convert rs485 bindings to json-schema
dt-bindings: serial: Convert STM32 UART to json-schema
Documentation/devicetree/bindings/serial/rs485.txt | 32 +--------
.../devicetree/bindings/serial/rs485.yaml | 45 ++++++++++++
.../devicetree/bindings/serial/st,stm32-uart.yaml | 80 ++++++++++++++++++++++
.../devicetree/bindings/serial/st,stm32-usart.txt | 57 ---------------
4 files changed, 126 insertions(+), 88 deletions(-)
create mode 100644 Documentation/devicetree/bindings/serial/rs485.yaml
create mode 100644 Documentation/devicetree/bindings/serial/st,stm32-uart.yaml
delete mode 100644 Documentation/devicetree/bindings/serial/st,stm32-usart.txt
--
2.15.0
next reply other threads:[~2020-01-22 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 9:55 Benjamin Gaignard [this message]
2020-01-22 9:55 ` [PATCH v2 1/2] dt-bindings: serial: Convert rs485 bindings to json-schema Benjamin Gaignard
2020-01-23 14:42 ` Rob Herring
2020-01-22 9:55 ` [PATCH v2 2/2] dt-bindings: serial: Convert STM32 UART " Benjamin Gaignard
2020-01-23 14:43 ` Rob Herring
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=20200122095558.22553-1-benjamin.gaignard@st.com \
--to=benjamin.gaignard@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=erwan.leray@st.com \
--cc=fabrice.gasnier@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@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 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).