From: Kamel Bouhara <kamel.bouhara@bootlin.com>
To: Rob Herring <robh+dt@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
linux-arm-kernel@lists.infradead.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Kamel Bouhara <kamel.bouhara@bootlin.com>
Subject: [PATCH 0/3] Add new Overkiz Kizbox3 support
Date: Fri, 11 Oct 2019 14:50:19 +0200 [thread overview]
Message-ID: <20191011125022.16329-1-kamel.bouhara@bootlin.com> (raw)
Add support for the Kizbox3 Overkiz SAS boards.
Those boards are based on the Atmel SAMA5D27 SoC.
Kamel Bouhara (3):
dt-bindings: Add vendor prefix for Overkiz SAS
dt-bindings: arm: at91: Document Kizbox3 HS board binding
ARM: at91: add Overkiz KIZBOX3 board
.../devicetree/bindings/arm/atmel-at91.yaml | 7 +
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/at91-kizbox3-hs.dts | 309 +++++++++++++
arch/arm/boot/dts/at91-kizbox3_common.dtsi | 412 ++++++++++++++++++
5 files changed, 731 insertions(+)
create mode 100644 arch/arm/boot/dts/at91-kizbox3-hs.dts
create mode 100644 arch/arm/boot/dts/at91-kizbox3_common.dtsi
--
2.23.0
next reply other threads:[~2019-10-11 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 12:50 Kamel Bouhara [this message]
2019-10-11 12:50 ` [PATCH 1/3] dt-bindings: Add vendor prefix for Overkiz SAS Kamel Bouhara
2019-10-15 22:46 ` Rob Herring
2019-10-11 12:50 ` [PATCH 2/3] dt-bindings: arm: at91: Document Kizbox3 HS board binding Kamel Bouhara
2019-10-15 22:47 ` Rob Herring
2019-10-11 12:50 ` [PATCH 3/3] ARM: at91: add Overkiz KIZBOX3 board Kamel Bouhara
2019-10-14 4:49 ` kbuild test robot
2019-10-16 8:08 ` [PATCH 0/3] Add new Overkiz Kizbox3 support Alexandre Belloni
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=20191011125022.16329-1-kamel.bouhara@bootlin.com \
--to=kamel.bouhara@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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).