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 0/2] at91: add support for Arietta G25
Date: Sun, 28 Jul 2019 23:04:01 +0200 [thread overview]
Message-ID: <20190728210403.2730-1-uwe@kleine-koenig.org> (raw)
Hello,
I now took the time to work on mainline support for the Arietta G25.
It boots fine on v5.3-rc1 apart from the issue I reported on the Linux
ARM list yesterday[1].
Best regards
Uwe
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2019-July/669167.html
Uwe Kleine-König (2):
dts: add vendor prefix "acme" for "Acme Systems srl"
ARM: dts: at91: add support for Arietta G25
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
arch/arm/boot/dts/at91sam9g25-arietta.dts | 86 +++++++++++++++++++
2 files changed, 88 insertions(+)
create mode 100644 arch/arm/boot/dts/at91sam9g25-arietta.dts
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next 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 Uwe Kleine-König [this message]
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 ` [PATCH 2/2] ARM: dts: at91: add support for Arietta G25 Uwe Kleine-König
2019-07-31 11:36 ` 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-1-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).