From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] ARM64: tegra: Add support for Google Pixel C
Date: Mon, 29 Feb 2016 07:54:24 +0100 [thread overview]
Message-ID: <20160229065424.GD23745@ulmo> (raw)
In-Reply-To: <1455020809-17531-1-git-send-email-jonathanh@nvidia.com>
On Tue, Feb 09, 2016 at 12:26:49PM +0000, Jon Hunter wrote:
> Add initial device-tree support for Google Pixel C (a.k.a. Smaug) based
> upon Tegra210 SoC with 3 GiB of LPDDR4 RAM.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
>
> Changes v2 -> v3:
> - Added PSCI information to enable all 4 CPUs on boot
>
> Changes v1 -> v2:
> - Removed console boot parameter and added stdout-path
> - Added 32k clock for PMC
>
> arch/arm64/boot/dts/nvidia/Makefile | 1 +
> arch/arm64/boot/dts/nvidia/tegra210-smaug.dts | 83 +++++++++++++++++++++++++++
> 2 files changed, 84 insertions(+)
> create mode 100644 arch/arm64/boot/dts/nvidia/tegra210-smaug.dts
Applied, thanks.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160229/5c33bdce/attachment.sig>
next prev parent reply other threads:[~2016-02-29 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 16:33 [PATCH V2] ARM64: tegra: Add support for Google Pixel C Jon Hunter
2016-02-09 12:26 ` [PATCH V3] " Jon Hunter
2016-02-11 8:32 ` Alexandre Courbot
2016-02-11 8:55 ` Jon Hunter
2016-02-11 11:35 ` Alexandre Courbot
2016-02-26 18:04 ` Andrew Bresticker
2016-02-29 6:54 ` Thierry Reding [this message]
2016-02-25 21:07 ` [PATCH V2] " Andrew Bresticker
2016-02-26 9:12 ` Jon Hunter
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=20160229065424.GD23745@ulmo \
--to=thierry.reding@gmail.com \
--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).