linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/3] ARM: dts: add Raspberry Pi 3 A+
Date: Fri, 16 Nov 2018 13:23:13 -0800	[thread overview]
Message-ID: <87a7m8d8e6.fsf@anholt.net> (raw)
In-Reply-To: <1542322805-6211-1-git-send-email-stefan.wahren@i2se.com>

Stefan Wahren <stefan.wahren@i2se.com> writes:

> This patch series adds support for the brand new Raspberry Pi 3 A+ .
>
> Changes in V2:
> - add missing Makefile change for arm64
>
> Stefan Wahren (3):
>   dt-bindings: bcm: Add Raspberry Pi 3 A+
>   ARM: dts: add Raspberry Pi 3 A+
>   arm64: dts: broadcom: Add reference to RPi 3 A+

Looks pretty reasonable, but I couldn't verify any of the contents --
the firmware repo doesn't have a DT file for it, and the published
schematics don't show most of the GPIO connections (sigh).  How did you
write/test this?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20181116/43b09e4b/attachment.sig>

  parent reply	other threads:[~2018-11-16 21:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 23:00 [PATCH V2 0/3] ARM: dts: add Raspberry Pi 3 A+ Stefan Wahren
2018-11-15 23:00 ` [PATCH V2 1/3] dt-bindings: bcm: Add " Stefan Wahren
2018-11-15 23:00 ` [PATCH V2 2/3] ARM: dts: add " Stefan Wahren
2018-12-14 21:49   ` Phil Elwell
2018-12-27 13:50     ` Stefan Wahren
2018-11-15 23:00 ` [PATCH V2 3/3] arm64: dts: broadcom: Add reference to RPi " Stefan Wahren
2018-11-15 23:00 ` [PATCH 0/3] ARM: dts: add Raspberry Pi " Stefan Wahren
2018-11-16 21:23 ` Eric Anholt [this message]
2018-11-16 22:43   ` [PATCH V2 " Stefan Wahren
2018-11-19 22:49     ` Eric Anholt

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=87a7m8d8e6.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=linux-arm-kernel@lists.infradead.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).