From: Alexandre Courbot <gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Olof Johansson <olofj-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V3] ARM64: tegra: Add support for Google Pixel C
Date: Thu, 11 Feb 2016 20:35:44 +0900 [thread overview]
Message-ID: <CAAVeFuKKGW9-0bO6wkCL=i7P0XJ4Mx44BD3A5EvN8G4sS1NyXA@mail.gmail.com> (raw)
In-Reply-To: <56BC4C91.6070409-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Thu, Feb 11, 2016 at 5:55 PM, Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> wrote:
>
> On 11/02/16 08:32, Alexandre Courbot wrote:
>> On Tue, Feb 9, 2016 at 9:26 PM, Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 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-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>>
>> I need to add "clk_ignore_unused=1" to the bootargs in order to avoid
>> a hang during boot, but otherwise can reach a serial console.
>
> Were you testing on -next? If so, you should not need that. Otherwise,
> please make sure you have this patch [0]. Thierry has included this in a
> clock fixes series that should turn up in main soon.
In one of my moments of stupidity, I was on 4.5-rc3. Adding the patch
you mention makes boot complete without issues.
Thanks,
Alex.
WARNING: multiple messages have this Message-ID (diff)
From: gnurou@gmail.com (Alexandre Courbot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] ARM64: tegra: Add support for Google Pixel C
Date: Thu, 11 Feb 2016 20:35:44 +0900 [thread overview]
Message-ID: <CAAVeFuKKGW9-0bO6wkCL=i7P0XJ4Mx44BD3A5EvN8G4sS1NyXA@mail.gmail.com> (raw)
In-Reply-To: <56BC4C91.6070409@nvidia.com>
On Thu, Feb 11, 2016 at 5:55 PM, Jon Hunter <jonathanh@nvidia.com> wrote:
>
> On 11/02/16 08:32, Alexandre Courbot wrote:
>> On Tue, Feb 9, 2016 at 9:26 PM, Jon Hunter <jonathanh@nvidia.com> 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>
>>
>> I need to add "clk_ignore_unused=1" to the bootargs in order to avoid
>> a hang during boot, but otherwise can reach a serial console.
>
> Were you testing on -next? If so, you should not need that. Otherwise,
> please make sure you have this patch [0]. Thierry has included this in a
> clock fixes series that should turn up in main soon.
In one of my moments of stupidity, I was on 4.5-rc3. Adding the patch
you mention makes boot complete without issues.
Thanks,
Alex.
next prev parent reply other threads:[~2016-02-11 11:35 UTC|newest]
Thread overview: 18+ 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-08 16:33 ` Jon Hunter
[not found] ` <1454949199-27050-1-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-02-09 12:26 ` [PATCH V3] " Jon Hunter
2016-02-09 12:26 ` Jon Hunter
[not found] ` <1455020809-17531-1-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-02-11 8:32 ` Alexandre Courbot
2016-02-11 8:32 ` Alexandre Courbot
[not found] ` <CAAVeFuJt+VdJb4S3PC-RXVFYhLnq7yF+dV_w5or=0ebG+LnnGw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-11 8:55 ` Jon Hunter
2016-02-11 8:55 ` Jon Hunter
[not found] ` <56BC4C91.6070409-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-02-11 11:35 ` Alexandre Courbot [this message]
2016-02-11 11:35 ` Alexandre Courbot
2016-02-26 18:04 ` Andrew Bresticker
2016-02-26 18:04 ` Andrew Bresticker
2016-02-29 6:54 ` Thierry Reding
2016-02-29 6:54 ` Thierry Reding
2016-02-25 21:07 ` [PATCH V2] " Andrew Bresticker
2016-02-25 21:07 ` Andrew Bresticker
[not found] ` <CAL1qeaHVuvwTkctEMo6TFggPPgqaQZDnKZGYn1QRUROpJ9Dhrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-26 9:12 ` Jon Hunter
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='CAAVeFuKKGW9-0bO6wkCL=i7P0XJ4Mx44BD3A5EvN8G4sS1NyXA@mail.gmail.com' \
--to=gnurou-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=olofj-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.