From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM64: tegra: Add chosen node for tegra132 norrin
Date: Mon, 25 Jan 2016 18:10:21 +0100 [thread overview]
Message-ID: <20160125171021.GB10182@ulmo> (raw)
In-Reply-To: <56A646BC.1010708@nvidia.com>
On Mon, Jan 25, 2016 at 04:01:00PM +0000, Jon Hunter wrote:
> Correcting ARM-SOC email address ..
You might have to resend so that the original patch shows up in the
ARM SoC maintainers' inbox.
Thierry
> On 25/01/16 15:57, Jon Hunter wrote:
> >
> > On 25/01/16 15:55, Jon Hunter wrote:
> >> The NVIDIA bootloader, nvtboot, expects the "chosen" node to be present
> >> in the device-tree blob and if it is not then it fails to boot the kernel.
> >> Add the chosen node so we can boot the kernel on Tegra132 Norrin with the
> >> nvtboot bootloader.
> >>
> >> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> >> Acked-by: Thierry Reding <treding@nvidia.com>
> >> ---
> >> Ideally, we would like to get this into v4.5 as a fix for Tegra132 Norrin
> >> so that we can enable booting this board as part of our automated testing
> >> setup for Tegra [0][1]. Thierry suggested I send this directly as a fix
> >> to ARM-SOC. Let me know if this is ok. I have not included a "fixes" as it
> >> may not be needed for all bootloaders, but if you need this we could put:
> >>
> >> Fixes: 0f279eb arm64: tegra: Add NVIDIA Tegra132 Norrin support
> >>
> >> [0] http://nvtb.github.io/linux/
> >> [1] http://nvtb.github.io/linux-next/
> >
> > Forgot to mentioned that the differences for v1 -> v2 are just some
> > minor corrections to the commit message.
> >
> > Jon
> >
> >> arch/arm64/boot/dts/nvidia/tegra132-norrin.dts | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/arch/arm64/boot/dts/nvidia/tegra132-norrin.dts b/arch/arm64/boot/dts/nvidia/tegra132-norrin.dts
> >> index 7dfe1c085966..62f33fc84e3e 100644
> >> --- a/arch/arm64/boot/dts/nvidia/tegra132-norrin.dts
> >> +++ b/arch/arm64/boot/dts/nvidia/tegra132-norrin.dts
> >> @@ -12,6 +12,8 @@
> >> rtc1 = "/rtc at 0,7000e000";
> >> };
> >>
> >> + chosen { };
> >> +
> >> memory {
> >> device_type = "memory";
> >> reg = <0x0 0x80000000 0x0 0x80000000>;
> >>
-------------- 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/20160125/b8a6182c/attachment-0001.sig>
prev parent reply other threads:[~2016-01-25 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:55 [PATCH V2] ARM64: tegra: Add chosen node for tegra132 norrin Jon Hunter
2016-01-25 15:57 ` Jon Hunter
2016-01-25 16:01 ` Jon Hunter
2016-01-25 17:10 ` Thierry Reding [this message]
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=20160125171021.GB10182@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).