From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv4 respin 2/6] ARM: HYP/non-sec: Fix the ARCH Timer frequency setting.
Date: Thu, 11 Dec 2014 11:39:03 -0800 [thread overview]
Message-ID: <5489F2D7.7060707@freescale.com> (raw)
In-Reply-To: <1416797048-3003-1-git-send-email-Li.Xiubo@freescale.com>
On 11/23/2014 06:44 PM, Xiubo Li wrote:
> For some SoCs, the system clock frequency may not equal to the
> ARCH Timer's frequency.
>
> This patch uses the CONFIG_TIMER_CLK_FREQ instead of
> CONFIG_SYS_CLK_FREQ, then the system clock macro and arch timer
> macor could be set separately and without interfering each other.
>
> Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> ---
>
> Hi Albert,
>
> I there is one mistake about the CONFIG_TIMER_CLK_FREQ defination for
> sun7i platform.
>
> So i respin this patch separately.
>
> Thanks,
>
> BRs
> Xiubo
>
I will have to merge the difference as a separated commit. Missed this one
because it wasn't assigned to me.
York
next prev parent reply other threads:[~2014-12-11 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 2:44 [U-Boot] [PATCHv4 respin 2/6] ARM: HYP/non-sec: Fix the ARCH Timer frequency setting Xiubo Li
2014-12-11 19:39 ` York Sun [this message]
2014-12-11 20:49 ` York Sun
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=5489F2D7.7060707@freescale.com \
--to=yorksun@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox