From: Minkyu Kang <mk7.kang@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] exynos: Set CNTFRQ
Date: Thu, 11 Feb 2016 11:17:42 +0900 [thread overview]
Message-ID: <56BBEF46.40205@samsung.com> (raw)
In-Reply-To: <1454359266-4290-1-git-send-email-agraf@suse.de>
Dear Alexander Graf,
On 02/02/16 05:41, Alexander Graf wrote:
> Commit 73a1cb27 moved the check whether we should set the architected
> timer frequency from CONFIG_SYS_CLK_FREQ to CONFIG_TIMER_CLK_FREQ, but
> did not update all users of it.
>
> The one where I (finally) realized why KVM didn't work is the Arndale
> board, so this patch adds the respective define to it.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> Fixes: 73a1cb27
> ---
> include/configs/exynos-common.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/configs/exynos-common.h b/include/configs/exynos-common.h
> index 852829c..c4e731f 100644
> --- a/include/configs/exynos-common.h
> +++ b/include/configs/exynos-common.h
> @@ -31,6 +31,7 @@
>
> /* input clock of PLL: 24MHz input clock */
> #define CONFIG_SYS_CLK_FREQ 24000000
> +#define CONFIG_TIMER_CLK_FREQ 24000000
patch looks good but,
Please make sure that it doesn't have a different value with system clock, always. (If you expected it)
#define CONFIG_TIMER_CLK_FREQ CONFIG_SYS_CLK_FREQ
>
> #define CONFIG_SETUP_MEMORY_TAGS
> #define CONFIG_CMDLINE_TAG
>
Thanks,
Minkyu Kang.
next prev parent reply other threads:[~2016-02-11 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 20:41 [U-Boot] [PATCH] exynos: Set CNTFRQ Alexander Graf
2016-02-02 0:05 ` Simon Glass
2016-02-11 2:17 ` Minkyu Kang [this message]
2016-03-10 13:18 ` [U-Boot] [PATCH v2] " Alexander Graf
2016-03-10 16:33 ` york sun
2016-03-10 16:35 ` york sun
2016-04-14 10:41 ` Minkyu Kang
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=56BBEF46.40205@samsung.com \
--to=mk7.kang@samsung.com \
--cc=u-boot@lists.denx.de \
/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.