From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/2] drivers: timer: inroduce ARC timer driver
Date: Mon, 21 Nov 2016 14:16:25 +0000 [thread overview]
Message-ID: <1479737728.4199.55.camel@synopsys.com> (raw)
In-Reply-To: <1478188344-23740-1-git-send-email-vzakhar@synopsys.com>
Hi Tom, Simon,
On Thu, 2016-11-03 at 18:52 +0300, Vlad Zakharov wrote:
> This patch series replaces legacy approach to access ARC timer
> via specific code in "arch/arc/lib/time.c" and uses timer
> driver instead.
>
> ARC cores may have up to 2 built-in timers: timer0 and timer1,
> usually at least one of them exists.
>
> They are controlled through auxiliary registers and so we
> don't have to remap their control registers as we used to do
> with MMIO registers of external peripheral devices.
>
> Cc: Simon Glass <sjg@chromium.org>
> ---
> Changes v1..v2
> ?- Minor clean-ups of code and comments.
> ?- Moved TIMER and ARC_TIMER config symbols from each defconfig to
> arch Kconfig file to avoid duplication
>
> Vlad Zakharov (2):
> ? drivers: timer: Introduce ARC timer driver
> ? arc: use timer driver instead of arch/arc/lib/timer.c
I'm wondering if you guys would like to accept this short
series in your tree or I may apply it on mine and send pull-request
to Tom later on?
-Alexey
next prev parent reply other threads:[~2016-11-21 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 15:52 [U-Boot] [PATCH v2 0/2] drivers: timer: inroduce ARC timer driver Vlad Zakharov
2016-11-03 15:52 ` [U-Boot] [PATCH v2 1/2] drivers: timer: Introduce " Vlad Zakharov
2016-11-03 15:52 ` [U-Boot] [PATCH v2 2/2] arc: use timer driver instead of arch/arc/lib/timer.c Vlad Zakharov
2016-11-21 14:16 ` Alexey Brodkin [this message]
2016-11-21 14:19 ` [U-Boot] [PATCH v2 0/2] drivers: timer: inroduce ARC timer driver Alexey Brodkin
2016-11-21 14:19 ` Tom Rini
2016-11-21 14:24 ` Alexey Brodkin
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=1479737728.4199.55.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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