From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: sunxi: Select HAVE_ARM_ARCH_TIMER
Date: Thu, 27 Mar 2014 14:42:42 -0700 [thread overview]
Message-ID: <7hy4zv71yl.fsf@paris.lan> (raw)
In-Reply-To: <1395934061-5340-1-git-send-email-maxime.ripard@free-electrons.com> (Maxime Ripard's message of "Thu, 27 Mar 2014 16:27:41 +0100")
Maxime Ripard <maxime.ripard@free-electrons.com> writes:
> In order for the architected timers support to be enabled in the kernel, this
> option has to be enabled. Otherwise, the architected timers driver won't be
> compiled in, and we will not get to use them.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
>
> Hi Arnd, Kevin, Olof,
>
> It would be great if you could apply this patch directly on top of the current
> arm-soc for-next.
Applied to next/soc, merged into for-next.
With this, merging Emilio's clk pull req in as a dependenency and
upgrading u-boot on my Cubie2 for the proper architected timer init, it
seems all the boot regressions on sunxi have disappeared.
Thanks,
Kevin
prev parent reply other threads:[~2014-03-27 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 15:27 [PATCH] ARM: sunxi: Select HAVE_ARM_ARCH_TIMER Maxime Ripard
2014-03-27 21:42 ` Kevin Hilman [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=7hy4zv71yl.fsf@paris.lan \
--to=khilman@linaro.org \
--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).