From: Jamie Iles <jamie@jamieiles.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: linux-kernel@vger.kernel.org, John Stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCHv3] x86, mrst: share APB timer code with other platforms
Date: Sun, 8 May 2011 18:16:17 +0100 [thread overview]
Message-ID: <20110508171617.GA2943@pulham.picochip.com> (raw)
In-Reply-To: <1302606630-12459-1-git-send-email-jamie@jamieiles.com>
On Tue, Apr 12, 2011 at 12:10:30PM +0100, Jamie Iles wrote:
> The APB timers are an IP block from Synopsys (DesignWare APB timers)
> and are also found in other systems including ARM SoC's. This patch
> adds functions for creating clock_event_devices and clocksources from
> APB timers but does not do the resource allocation. This is handled
> in a higher layer to allow the timers to be created from multiple
> methods such as platform_devices.
>
> Changes since v2:
> - Make eoi() for clock_event_device optional for x86 where eoi
> is handled in firmware.
> Changes since v1:
> - Use the correct timer for clocksource on x86
> - Select the correct timer rating for x86
> - Restore freerunning timer behaviour for oneshot event devices
> - Reenable event irq correctly for hotplug
>
> Cc: John Stultz <johnstul@us.ibm.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>
> Signed-off-by: Jamie Iles <jamie@jamieiles.com>
Ping?
Jamie
next prev parent reply other threads:[~2011-05-08 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 11:10 [PATCHv3] x86, mrst: share APB timer code with other platforms Jamie Iles
2011-05-08 17:16 ` Jamie Iles [this message]
2011-05-09 17:55 ` Jacob Pan
2011-05-09 20:22 ` john stultz
2011-05-09 20:50 ` Jamie Iles
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=20110508171617.GA2943@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).