From: mani@kernel.org
To: robh+dt@kernel.org, mcoquelin.stm32@gmail.com, alexandre.torgue@st.com
Cc: devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Manivannan Sadhasivam <mani@kernel.org>
Subject: [PATCH v2 0/6] Add Stinger96 and IoT Box board support
Date: Sun, 3 May 2020 21:12:09 +0530 [thread overview]
Message-ID: <20200503154215.23654-1-mani@kernel.org> (raw)
From: Manivannan Sadhasivam <mani@kernel.org>
Hello,
This series adds Stinger96 and IoT Box board support. These boards are
based on STM32MP157A SoC, designed and manufactured by Shiratech solutions.
The Stinger96 is a base board (96Boards IoT Extended edition) while IoT Box
adds one mezzanine on top of it and sold as a gateway device.
This series depends on below patchsets already submitted and gone through
reviews:
[PATCH v3 0/3] Add Reset and Wakeup support for CCS811
[PATCH v3 0/2] Add CTS/RTS gpio support to STM32 UART
More information about these boards can be found in below links:
https://www.shiratech-solutions.com/products/stinger96/
https://www.shiratech-solutions.com/products/iot-box/
Thanks,
Mani
Changes in v2:
* Used "stm32" prefix for all DT commits
* Dropped custom sdmmc2 pinctrl node since existing node itself has pullup
enabled and works fine.
Manivannan Sadhasivam (6):
dt-bindings: Add vendor prefix for Shiratech Solutions
ARM: dts: stm32: Add missing pinctrl entries for STM32MP15
dt-bindings: arm: stm32: Document Stinger96 compatible
ARM: dts: stm32: Add Stinger96 board support
dt-bindings: arm: stm32: Document IoT Box compatible
ARM: dts: stm32: Add IoT Box board support
.../devicetree/bindings/arm/stm32/stm32.yaml | 2 +
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
arch/arm/boot/dts/Makefile | 2 +
arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 64 ++++
arch/arm/boot/dts/stm32mp157a-iot-box.dts | 68 ++++
arch/arm/boot/dts/stm32mp157a-stinger96.dts | 12 +
arch/arm/boot/dts/stm32mp157a-stinger96.dtsi | 342 ++++++++++++++++++
7 files changed, 492 insertions(+)
create mode 100644 arch/arm/boot/dts/stm32mp157a-iot-box.dts
create mode 100644 arch/arm/boot/dts/stm32mp157a-stinger96.dts
create mode 100644 arch/arm/boot/dts/stm32mp157a-stinger96.dtsi
--
2.17.1
next reply other threads:[~2020-05-03 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 15:42 mani [this message]
2020-05-03 15:42 ` [PATCH v2 1/6] dt-bindings: Add vendor prefix for Shiratech Solutions mani
2020-05-12 22:10 ` Rob Herring
2020-05-03 15:42 ` [PATCH v2 2/6] ARM: dts: stm32: Add missing pinctrl entries for STM32MP15 mani
2020-05-03 15:42 ` [PATCH v2 3/6] dt-bindings: arm: stm32: Document Stinger96 compatible mani
2020-05-12 22:11 ` Rob Herring
2020-05-03 15:42 ` [PATCH v2 4/6] ARM: dts: stm32: Add Stinger96 board support mani
2020-05-03 15:42 ` [PATCH v2 5/6] dt-bindings: arm: stm32: Document IoT Box compatible mani
2020-05-12 22:11 ` Rob Herring
2020-05-03 15:42 ` [PATCH v2 6/6] ARM: dts: stm32: Add IoT Box board support mani
2020-05-14 12:38 ` [PATCH v2 0/6] Add Stinger96 and " 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=20200503154215.23654-1-mani@kernel.org \
--to=mani@kernel.org \
--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=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).