From: "Uwe Kleine-König" <uwe@kleine-koenig.org>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: devicetree@vger.kernel.org, info@acmesystems.it,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: at91: add support for Arietta G25
Date: Sun, 28 Jul 2019 23:04:03 +0200 [thread overview]
Message-ID: <20190728210403.2730-3-uwe@kleine-koenig.org> (raw)
In-Reply-To: <20190728210403.2730-1-uwe@kleine-koenig.org>
The Arietta G25 is a SBC powered by a AT91SAMG25 running at 400 MHz.
See https://www.acmesystems.it/arietta for more details.
Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
---
arch/arm/boot/dts/at91sam9g25-arietta.dts | 86 +++++++++++++++++++++++
1 file changed, 86 insertions(+)
create mode 100644 arch/arm/boot/dts/at91sam9g25-arietta.dts
diff --git a/arch/arm/boot/dts/at91sam9g25-arietta.dts b/arch/arm/boot/dts/at91sam9g25-arietta.dts
new file mode 100644
index 000000000000..6c20e02f0ea9
--- /dev/null
+++ b/arch/arm/boot/dts/at91sam9g25-arietta.dts
@@ -0,0 +1,86 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * Arietta - System On Module
+ * https://www.acmesystems.it/arietta
+ */
+
+/dts-v1/;
+#include "at91sam9g25.dtsi"
+
+/ {
+ model = "Acme Systems Arietta G25";
+ compatible = "acme,ariettag25", "atmel,at91sam9x5", "atmel,at91sam9";
+
+ chosen {
+ stdout-path = "serial0:115200n8";
+ };
+
+ memory {
+ reg = <0x20000000 0x8000000>;
+ };
+
+ clocks {
+ slow_xtal {
+ clock-frequency = <32768>;
+ };
+
+ main_xtal {
+ clock-frequency = <12000000>;
+ };
+ };
+
+ ahb {
+ apb {
+ rtc@fffffeb0 {
+ status = "okay";
+ };
+ };
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+ arietta_led {
+ label = "arietta_led";
+ gpios = <&pioB 8 GPIO_ACTIVE_HIGH>;
+ linux,default-trigger = "heartbeat";
+ };
+ };
+};
+
+&dbgu {
+ status = "okay";
+};
+
+&mmc0 {
+ pinctrl-0 = <
+ &pinctrl_mmc0_slot0_clk_cmd_dat0
+ &pinctrl_mmc0_slot0_dat1_3>;
+ status = "okay";
+
+ slot@0 {
+ reg = <0>;
+ bus-width = <4>;
+ };
+};
+
+&usart0 {
+ status ="okay";
+};
+
+&usart1 {
+ status ="okay";
+};
+
+&usb0 {
+ status = "okay";
+ num-ports = <3>;
+};
+
+&usb1 {
+ status = "okay";
+};
+
+&usb2 {
+ status = "okay";
+};
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-28 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 21:04 [PATCH 0/2] at91: add support for Arietta G25 Uwe Kleine-König
2019-07-28 21:04 ` [PATCH 1/2] dts: add vendor prefix "acme" for "Acme Systems srl" Uwe Kleine-König
2019-07-29 22:34 ` Rob Herring
2019-07-31 11:34 ` Ludovic Desroches
2019-07-31 21:48 ` Uwe Kleine-König
2019-08-12 20:54 ` Alexandre Belloni
2019-07-28 21:04 ` Uwe Kleine-König [this message]
2019-07-31 11:36 ` [PATCH 2/2] ARM: dts: at91: add support for Arietta G25 Ludovic Desroches
2019-07-31 13:18 ` Ludovic Desroches
2019-07-31 12:27 ` Stefan Wahren
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=20190728210403.2730-3-uwe@kleine-koenig.org \
--to=uwe@kleine-koenig.org \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=info@acmesystems.it \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ludovic.desroches@microchip.com \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@microchip.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).