From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] timer: Add High Precision Event Timers (HPET) support
Date: Thu, 29 Mar 2018 13:52:10 +0300 [thread overview]
Message-ID: <1522320730.21176.56.camel@linux.intel.com> (raw)
In-Reply-To: <20180329005844.GA63828@intel.com>
On Wed, 2018-03-28 at 17:58 -0700, Ivan Gorinov wrote:
> Adding HPET as an alternative timer for x86 (default is TSC).
> HPET main counter has constant clock frequency, calibration is not
> required.
> This change also makes TSC timer driver optional on x86 platforms.
> If X86_TSC is disabled, early timer functions are provided by HPET.
>
> HPET can be selected as the tick timer in the Device Tree "chosen"
> node:
>
> /include/ "hpet.dtsi"
>
> chosen {
> tick-timer = "/hpet0";
> };
>
First question is how this will work in case of Broadwell and Ivybridge
that have something to do with HPET in their CPU code, i.e.
arch/x86/cpu/broadwell/pch.c
arch/x86/cpu/ivybridge/lpc.c
?
Look for
clrsetbits_le32(RCB_REG(HPTC), 3, 1 << 7);
> +static int hpet_timer_get_count(struct udevice *dev, u64 *count)
> +static int hpet_timer_probe(struct udevice *dev)
> +#ifndef CONFIG_X86_TSC_TIMER
> +#define EARLY_HPET_BASE 0xfed00000
HPET address is fixed, AFAIU, on x86, and provided by config option in
U-Boot.
> +unsigned long notrace timer_early_get_rate(void)
> +u64 notrace timer_early_get_count(void)
> +int timer_init(void)
These functions have too much code duplication with above.
> +#endif
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-03-29 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 0:58 [U-Boot] [PATCH] timer: Add High Precision Event Timers (HPET) support Ivan Gorinov
2018-03-29 10:52 ` Andy Shevchenko [this message]
2018-03-29 22:29 ` Ivan Gorinov
2018-03-29 22:39 ` Simon Glass
2018-03-30 19:42 ` Andy Shevchenko
2018-03-31 0:24 ` Ivan Gorinov
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=1522320730.21176.56.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.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