From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH CFT] ARM: orion: implement ARM delay timer
Date: Wed, 27 Jan 2016 10:52:54 +0100 [thread overview]
Message-ID: <87twlz9wnd.fsf@free-electrons.com> (raw)
In-Reply-To: <20160127094533.GW10826@n2100.arm.linux.org.uk> (Russell King's message of "Wed, 27 Jan 2016 09:45:33 +0000")
Hi Russell King,
On mer., janv. 27 2016, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> On Wed, Jan 27, 2016 at 08:58:50AM +0100, Gregory CLEMENT wrote:
>> Hi Russell,
>>
>> On lun., oct. 19 2015, Russell King <rmk+kernel@arm.linux.org.uk> wrote:
>>
>> > Implement an ARM delay timer to be used for udelay() on orion legacy
>> > platforms. This allows us to skip the delay loop calibration at boot.
>> >
>> > It also means that udelay() will be unaffected by CPU frequency changes
>> > when cpufreq is enabled on these platforms.
>> >
>> > Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
>>
>> Applied on mvebu/drivers with Acked-by tag from Andrew Lunn
>
> And, I hope, my tested-by which delayed Andrew's ack until December,
Now yes :)
Gregory
> despite the patch being marked as CFT because I wanted _others_ to
> test it (which never happened.)
>
> --
> RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
> according to speedtest.net.
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2016-01-27 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 16:13 [PATCH CFT] ARM: orion: implement ARM delay timer Russell King
2015-12-07 10:19 ` Russell King - ARM Linux
2015-12-07 14:03 ` Andrew Lunn
2015-12-07 15:00 ` Russell King - ARM Linux
2015-12-07 15:09 ` Andrew Lunn
2016-01-27 7:58 ` Gregory CLEMENT
2016-01-27 9:45 ` Russell King - ARM Linux
2016-01-27 9:52 ` Gregory CLEMENT [this message]
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=87twlz9wnd.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.