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 v3 0/6] Armada 370/XP clocksource fixes
Date: Tue, 13 Aug 2013 16:07:14 +0200	[thread overview]
Message-ID: <520A3D92.20006@linaro.org> (raw)
In-Reply-To: <20130813140509.GA2359@localhost>

On 08/13/2013 04:05 PM, Ezequiel Garcia wrote:
> On Tue, Aug 13, 2013 at 02:28:41PM +0200, Daniel Lezcano wrote:
>> On 08/12/2013 09:16 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 v3.11-rc4. Also, to ease maintainer's task this
>>> is based on these two patches which are in linux-next:
>>>
>>>   commit be14114934545f52be2ffddbe401ba0951007c59
>>>   Author: Stephen Boyd <sboyd@codeaurora.org>
>>>   "clocksource: time-armada-370-xp: Divorce from local timer API"
>>>
>>>   commit 4047c794ae18c467a5ea987265238186bc253f61
>>>   Author: Stephen Boyd <sboyd@codeaurora.org>
>>>   "clocksource: time-armada-370-xp: Fix sparse warning"
>>
>> Your patchset does not apply to my tree for timers/core
>>
>> These two patches described above are in the ARM tree, not available in
>> the timers/core tree.
>>
>> The correct submission path for these would have been through timers/urgent:
>>
>> timers/urgent -> v3.11-rcX -> arm-soc
>>                            -> timers/core
>>
>> Or alternatively if it depends on material in arm-soc, a pull request
>> based in a v3.11-rcX where Olof and I can pull from.
>>
>> I guess you have to rebase your patchset on top of timers/core.
>>
> 
> Sure. I'll just send this patchset on top of timers/core.

Ok, thx.

> I guess it was just a silly thing to base this on top of those
> two patches.
> 
> Thanks,
> 


-- 
 <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

      reply	other threads:[~2013-08-13 14:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 19:16 [PATCH v3 0/6] Armada 370/XP clocksource fixes Ezequiel Garcia
2013-08-12 19:16 ` [PATCH v3 1/6] clocksource: armada-370-xp: Use BIT() Ezequiel Garcia
2013-08-12 19:16 ` [PATCH v3 2/6] clocksource: armada-370-xp: Simplify TIMER_CTRL register access Ezequiel Garcia
2013-08-12 19:16 ` [PATCH v3 3/6] clocksource: armada-370-xp: Use CLOCKSOURCE_OF_DECLARE Ezequiel Garcia
2013-08-12 19:16 ` [PATCH v3 4/6] clocksource: armada-370-xp: Introduce new compatibles Ezequiel Garcia
2013-08-12 19:16 ` [PATCH v3 5/6] clocksource: armada-370-xp: Fix device-tree binding Ezequiel Garcia
2013-08-12 19:20   ` Jason Cooper
2013-08-12 19:16 ` [PATCH v3 6/6] ARM: mvebu: Fix the Armada 370/XP timer compatible strings Ezequiel Garcia
2013-08-13 12:28 ` [PATCH v3 0/6] Armada 370/XP clocksource fixes Daniel Lezcano
2013-08-13 14:05   ` Ezequiel Garcia
2013-08-13 14:07     ` Daniel Lezcano [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=520A3D92.20006@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).