From: Benjamin Gaignard <benjamin.gaignard@st.com>
To: <mcoquelin.stm32@gmail.com>, <alexandre.torgue@st.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH v2 0/3] Convert STM32 dma to json-schema
Date: Wed, 18 Dec 2019 15:48:41 +0100 [thread overview]
Message-ID: <20191218144844.7481-1-benjamin.gaignard@st.com> (raw)
version 2: Only contains rebased dtsi file on top of stm32-next after
DT diversity patches
This series convert STM32 dma, mdma and dmamux bindings to json-schema.
Yaml bindings use dma-controller and dma-router schemas where nodes names
are verified which lead to fix stm32f746, stm32f743 and stm32mp157 device
tree files.
Benjamin Gaignard (3):
ARM: dts: stm32: fix dma controller node name on stm32f746
ARM: dts: stm32: fix dma controller node name on stm32f743
ARM: dts: stm32: fix dma controller node name on stm32mp157c
arch/arm/boot/dts/stm32f746.dtsi | 4 ++--
arch/arm/boot/dts/stm32h743.dtsi | 6 +++---
arch/arm/boot/dts/stm32mp151.dtsi | 6 +++---
3 files changed, 8 insertions(+), 8 deletions(-)
--
2.15.0
next reply other threads:[~2019-12-18 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 14:48 Benjamin Gaignard [this message]
2019-12-18 14:48 ` [PATCH v2 1/3] ARM: dts: stm32: fix dma controller node name on stm32f746 Benjamin Gaignard
2019-12-18 14:48 ` [PATCH v2 2/3] ARM: dts: stm32: fix dma controller node name on stm32f743 Benjamin Gaignard
2019-12-18 14:48 ` [PATCH v2 3/3] ARM: dts: stm32: fix dma controller node name on stm32mp157c Benjamin Gaignard
2019-12-18 16:47 ` [PATCH v2 0/3] Convert STM32 dma to json-schema Alexandre Torgue
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=20191218144844.7481-1-benjamin.gaignard@st.com \
--to=benjamin.gaignard@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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).