linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/6] Armada 370/XP clocksource fixes
Date: Tue, 13 Aug 2013 18:22:48 +0200	[thread overview]
Message-ID: <520A5D58.10902@linaro.org> (raw)
In-Reply-To: <1376404995-24548-1-git-send-email-ezequiel.garcia@free-electrons.com>

On 08/13/2013 04:43 PM, Ezequiel Garcia wrote:
> This small patchset fixes a somewhat minor issue found in the clocksource
> driver for Armada 370/XP SoC.
> 
> On one side the Armada 370 SoC has no 25 MHz fixed timer.
> On the other side the Armada XP SoC cannot work properly without such 25 MHz
> fixed timer selected, because otherwise the base clock frequency would vary
> when doing cpufreq frequency changes.
> 
> Therefore we can consider the SoCs as not being compatible, being better to
> have two compatible strings, one for each SoC. The previous compatible and
> its behavior has been removed, considering there are no DT-enabled boards
> in use in the field.
> 
> In addition, CLOCKSOURCE_OF_DECLARE is used to simplify the initialization.
> 
> This patchset is based on tip/timers/core.
> 

Applied to my tree as 3.12 material.

Thanks
  -- Daniel

-- 
 <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  parent reply	other threads:[~2013-08-13 16:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 14:43 [PATCH v4 0/6] Armada 370/XP clocksource fixes Ezequiel Garcia
2013-08-13 14:43 ` [PATCH v4 1/6] clocksource: armada-370-xp: Use BIT() Ezequiel Garcia
2013-08-13 14:43 ` [PATCH v4 2/6] clocksource: armada-370-xp: Simplify TIMER_CTRL register access Ezequiel Garcia
2013-08-13 14:43 ` [PATCH v4 3/6] clocksource: armada-370-xp: Use CLOCKSOURCE_OF_DECLARE Ezequiel Garcia
2013-08-13 14:43 ` [PATCH v4 4/6] clocksource: armada-370-xp: Introduce new compatibles Ezequiel Garcia
2013-08-13 14:43 ` [PATCH v4 5/6] clocksource: armada-370-xp: Fix device-tree binding Ezequiel Garcia
2013-08-14 15:26   ` Mark Rutland
2013-08-15 16:27     ` Ezequiel Garcia
2013-08-16 23:29       ` Stephen Warren
2013-08-17 12:09         ` Tomasz Figa
2013-08-17 12:29           ` Sebastian Hesselbarth
2013-08-17 12:34             ` Tomasz Figa
2013-08-17 16:43             ` Ezequiel Garcia
2013-08-18 23:33               ` Sebastian Hesselbarth
2013-08-18 23:01                 ` Tomasz Figa
2013-08-19 16:39                   ` Ezequiel Garcia
2013-08-19  1:35                 ` Ezequiel Garcia
2013-08-17 16:38         ` Ezequiel Garcia
2013-08-13 14:43 ` [PATCH v4 6/6] ARM: mvebu: Fix the Armada 370/XP timer compatible strings Ezequiel Garcia
2013-08-13 19:26   ` Jason Cooper
2013-08-13 16:22 ` Daniel Lezcano [this message]
2013-08-13 16:52   ` [PATCH v4 0/6] Armada 370/XP clocksource fixes Jason Cooper
2013-08-13 17:48     ` Daniel Lezcano
2013-08-13 17:58       ` Jason Cooper
2013-08-13 18:04         ` Daniel Lezcano
2013-08-13 18:08           ` Jason Cooper
2013-08-20 12:44   ` Ezequiel Garcia

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=520A5D58.10902@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --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).