From: Alain Volmat <avolmat@me.com>
To: Patrice Chotard <patrice.chotard@st.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, avolmat@me.com
Subject: [PATCH v2 0/3] Introduction of STiH418 based 4KOpen board
Date: Fri, 29 Jan 2021 08:34:44 +0100 [thread overview]
Message-ID: <20210129073447.18778-1-avolmat@me.com> (raw)
This serie introduces the 4KOpen (stih418-b2264) board based
on a stih418 soc. Since it is the first board to use the spi-fsm
SPI NOR controller available since stih407, the controller is
also added within the stih407-family DT.
It also contains a fix within the stih418 DT since the rng11 is not
available on this platform and is thus disabled.
Alain Volmat (3):
ARM: dts: sti: add the spinor controller node within stih407-family
ARM: dts: sti: disable rng11 on the stih418 platform
ARM: dts: sti: Introduce 4KOpen (stih418-b2264) board
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/stih407-family.dtsi | 15 ++++
arch/arm/boot/dts/stih418-b2264.dts | 123 ++++++++++++++++++++++++++
arch/arm/boot/dts/stih418.dtsi | 4 +
4 files changed, 144 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/stih418-b2264.dts
next reply other threads:[~2021-01-29 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 7:34 Alain Volmat [this message]
2021-01-29 7:34 ` [PATCH v2 1/3] ARM: dts: sti: add the spinor controller node within stih407-family Alain Volmat
2021-01-29 7:34 ` [PATCH v2 2/3] ARM: dts: sti: disable rng11 on the stih418 platform Alain Volmat
2021-01-29 7:34 ` [PATCH v2 3/3] ARM: dts: sti: Introduce 4KOpen (stih418-b2264) board Alain Volmat
-- strict thread matches above, loose matches on Subject: below --
2021-01-29 7:27 [PATCH v2 0/3] Introduction of STiH418 based 4KOpen board Alain Volmat
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=20210129073447.18778-1-avolmat@me.com \
--to=avolmat@me.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@st.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
all inboxes | Powered by JetHome®