From: Oleksij Rempel <o.rempel@pengutronix.de>
To: "Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] mainline Protonic PRTT1x boards
Date: Tue, 26 Apr 2022 09:35:07 +0200 [thread overview]
Message-ID: <20220426073511.1160119-1-o.rempel@pengutronix.de> (raw)
changes v4:
- reorder prtt1X compatible again
- remove spaces in stm32mp151a-prtt1c.dts
changes v3:
- add silabs,wfx compatible
- move spi pin configuration to stm32mp15-pinctrl.dtsi
- move prtt1X compatible in alphabetical order
- add watchdog and thermal nodes
changes v2:
- cleanup mmc nodes
- disabled dma for uart4 (this is console interface and it should work
as simple as possible)
Oleksij Rempel (4):
dt-bindings: arm: stm32: Add compatible strings for Protonic T1L
boards
dt-bindings: net: silabs,wfx: add prt,prtt1c-wfm200 antenna variant
ARM: dts: stm32: stm32mp15-pinctrl: add spi1-1 pinmux group
ARM: dts: stm32: add support for Protonic PRTT1x boards
.../devicetree/bindings/arm/stm32/stm32.yaml | 8 +
.../staging/net/wireless/silabs,wfx.yaml | 1 +
arch/arm/boot/dts/Makefile | 3 +
arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 15 +
arch/arm/boot/dts/stm32mp151a-prtt1a.dts | 52 +++
arch/arm/boot/dts/stm32mp151a-prtt1c.dts | 304 ++++++++++++++++++
arch/arm/boot/dts/stm32mp151a-prtt1l.dtsi | 229 +++++++++++++
arch/arm/boot/dts/stm32mp151a-prtt1s.dts | 63 ++++
8 files changed, 675 insertions(+)
create mode 100644 arch/arm/boot/dts/stm32mp151a-prtt1a.dts
create mode 100644 arch/arm/boot/dts/stm32mp151a-prtt1c.dts
create mode 100644 arch/arm/boot/dts/stm32mp151a-prtt1l.dtsi
create mode 100644 arch/arm/boot/dts/stm32mp151a-prtt1s.dts
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-04-26 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 7:35 Oleksij Rempel [this message]
2022-04-26 7:35 ` [PATCH v4 1/4] dt-bindings: arm: stm32: Add compatible strings for Protonic T1L boards Oleksij Rempel
2022-04-28 7:52 ` Krzysztof Kozlowski
2022-04-26 7:35 ` [PATCH v4 2/4] dt-bindings: net: silabs, wfx: add prt, prtt1c-wfm200 antenna variant Oleksij Rempel
2022-04-28 7:52 ` [PATCH v4 2/4] dt-bindings: net: silabs,wfx: add prt,prtt1c-wfm200 " Krzysztof Kozlowski
2022-04-26 7:35 ` [PATCH v4 3/4] ARM: dts: stm32: stm32mp15-pinctrl: add spi1-1 pinmux group Oleksij Rempel
2022-04-26 7:35 ` [PATCH v4 4/4] ARM: dts: stm32: add support for Protonic PRTT1x boards Oleksij Rempel
2022-05-02 8:40 ` [PATCH v4 0/4] mainline " 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=20220426073511.1160119-1-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=jerome.pouiller@silabs.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@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).