linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] clocksource: sun5i: Support parent clock rate changes
Date: Thu, 19 Mar 2015 23:53:44 +0100	[thread overview]
Message-ID: <20150319225344.GF4255@lukather> (raw)
In-Reply-To: <1425550856-12928-1-git-send-email-maxime.ripard@free-electrons.com>

Hi Daniel,

On Thu, Mar 05, 2015 at 11:20:51AM +0100, Maxime Ripard wrote:
> Hi,
> 
> The Allwinner HS timers have the AHB clock as their parent
> clock. Since this clock is shared with other devices, we could very
> well have another driver requesting a rate change of that clock,
> making our timer change frequency at the same time.
> 
> This is especially true on the A31, where the DMA controller needs to
> do such a rate change, making the HS timer unreliable at the time on
> the A31.
> 
> This serie makes some cleanups and implements clock notifiers to be
> able to reflect such rate changes and make sure that the timer is
> always working.
> 
> Maxime
> 
> Changes from v2:
>   - Rebased on top of v4.0-rc1
>   - Removed the local_irq_save/restore around clockevents_update_freq
> 
> Changes from v1:
>   - Changed the interrupt name to its previous value
> 
> Maxime Ripard (5):
>   clocksource: sun5i: Switch to request_irq
>   clocksource: sun5i: Use of_io_request_and_map
>   clocksource: sun5i: Remove sched_clock
>   clocksource: sun5i: Refactor the current code
>   clocksource: sun5i: Add clock notifiers

Have these patches been merged?

If not, it woulde be great if the third one ("clocksource: sun5i:
Remove sched_clock") was merged for 4.0.

The sched_clock we use on some system is this timer's, and since we
started using cpufreq, the cpu clock (that is one of the timer's clock
indirect parent) now changes, along with the actual sched_clock rate.

We can safely remove the sched_clock on those systems, since we have
other reliable sched_clock in the system.

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150319/de221ac2/attachment.sig>

  parent reply	other threads:[~2015-03-19 22:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 10:20 [PATCH v3 0/5] clocksource: sun5i: Support parent clock rate changes Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 1/5] clocksource: sun5i: Switch to request_irq Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 2/5] clocksource: sun5i: Use of_io_request_and_map Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 3/5] clocksource: sun5i: Remove sched_clock Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 4/5] clocksource: sun5i: Refactor the current code Maxime Ripard
2015-03-05 14:30   ` Daniel Lezcano
2015-03-05 14:32     ` [PATCH] " Daniel Lezcano
2015-03-05 15:44       ` Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 5/5] clocksource: sun5i: Add clock notifiers Maxime Ripard
2015-03-19 22:53 ` Maxime Ripard [this message]
2015-03-20 14:04   ` [PATCH v3 0/5] clocksource: sun5i: Support parent clock rate changes Daniel Lezcano
2015-03-20 20:56     ` Maxime Ripard
2015-03-21 10:43       ` Hans de Goede
2015-03-23 16:54         ` Maxime Ripard

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=20150319225344.GF4255@lukather \
    --to=maxime.ripard@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 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).