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 3/6] dt-bindings: arm: stm32: Document Stinger96 compatible
Date: Mon, 20 Apr 2020 23:01:21 +0530 [thread overview]
Message-ID: <20200420173124.27416-4-mani@kernel.org> (raw)
In-Reply-To: <20200420173124.27416-1-mani@kernel.org>
From: Manivannan Sadhasivam <mani@kernel.org>
Document devicetree compatible of Shiratech Stinger96 board.
Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
---
Documentation/devicetree/bindings/arm/stm32/stm32.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/stm32/stm32.yaml b/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
index 71ea3f04ab9c..3849f1d0e03e 100644
--- a/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
+++ b/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
@@ -39,6 +39,7 @@ properties:
- enum:
- arrow,stm32mp157a-avenger96 # Avenger96
- lxa,stm32mp157c-mc1
+ - shiratech,stm32mp157a-stinger96 # Stinger96
- st,stm32mp157c-ed1
- st,stm32mp157a-dk1
- st,stm32mp157c-dk2
--
2.17.1
next prev parent reply other threads:[~2020-04-20 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 17:31 [PATCH 0/6] Add Stinger96 and IoT Box board support mani
2020-04-20 17:31 ` [PATCH 1/6] dt-bindings: Add vendor prefix for Shiratech Solutions mani
2020-04-20 17:31 ` [PATCH 2/6] ARM: dts: Add missing pinctrl entries for STM32MP15 mani
2020-04-21 11:16 ` Alexandre Torgue
2020-04-20 17:31 ` mani [this message]
2020-04-20 17:31 ` [PATCH 4/6] ARM: dts: stm32mp1: Add Stinger96 board support mani
2020-04-20 17:31 ` [PATCH 5/6] dt-bindings: arm: stm32: Document IoT Box compatible mani
2020-04-20 17:31 ` [PATCH 6/6] ARM: dts: stm32mp1: Add IoT Box board support mani
2020-04-29 8:02 ` 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=20200420173124.27416-4-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).