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 0/2] Marvell Armada 375 and 38x timer support
Date: Tue, 11 Feb 2014 14:09:03 +0100	[thread overview]
Message-ID: <52FA20EF.30807@linaro.org> (raw)
In-Reply-To: <20140211130758.GX8533@titan.lakedaemon.net>

On 02/11/2014 02:07 PM, Jason Cooper wrote:
> Daniel,
>
> On Tue, Feb 11, 2014 at 02:03:57PM +0100, Daniel Lezcano wrote:
>> On 02/10/2014 08:07 PM, Ezequiel Garcia wrote:
>>> Hello Daniel,
>>>
>>> This small series adds support for the two new Marvell ARM SoCs:
>>> the Armada 375 and Armada 38x.
>>>
>>> These new SoCs are based on Cortex-A9 CPU cores, and share a
>>> number of peripherals with their predecessors in the mach-mvebu
>>> family. The core support (arch/arm/mach-mvebu) for these SOCs have just
>>> been posted, and we're aiming at having this merged for 3.15.
>>>
>>> The A375 SoC timer is modeled matching the A370 timer, while the
>>> A38x SoC timer is modeled matching the AXP timer. However, we'd like
>>> to keep the compatible strings as SoC-specific.
>>>
>>> In the past, we've had trouble chosing a common compatible string, resulting
>>> in the introduction of per-SoC compatibles. Such compatible-string change
>>> of course implies breaking backards compatibility, and was only possible
>>> after agreeing that the old compatible wasn't used in production.
>>>
>>> So, in order to avoid such problems, we think it's better to keep them
>>> separate.
>>>
>>> Gregory CLEMENT (2):
>>>    clocksource: armada-370-xp: Add support for Armada 375
>>>    clocksource: armada-370-xp: Add support for Armada 38x
>>>
>>>   .../bindings/timer/marvell,armada-370-xp-timer.txt | 13 ++++++++----
>>>   drivers/clocksource/time-armada-370-xp.c           | 23 +++++++++++++++++++++-
>>>   2 files changed, 31 insertions(+), 5 deletions(-)
>>
>> Applied to my tree for 3.15.
>
> Please hold off until we've resolved the discussion regarding adding
> unneeded compatible strings.  It's under patch 6 in the main series
> adding support for this new SoC.
>
>    [PATCH 06/11] ARM: mvebu: add Armada 380/385 support to the system-controller driver

Ok, thanks for the heads up.

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

  reply	other threads:[~2014-02-11 13:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 19:07 [PATCH 0/2] Marvell Armada 375 and 38x timer support Ezequiel Garcia
2014-02-10 19:07 ` [PATCH 1/2] clocksource: armada-370-xp: Add support for Armada 375 Ezequiel Garcia
2014-02-10 19:07 ` [PATCH 2/2] clocksource: armada-370-xp: Add support for Armada 38x Ezequiel Garcia
2014-02-11 13:03 ` [PATCH 0/2] Marvell Armada 375 and 38x timer support Daniel Lezcano
2014-02-11 13:07   ` Jason Cooper
2014-02-11 13:09     ` Daniel Lezcano [this message]
2014-02-11 13:53       ` Ezequiel Garcia
2014-02-11 13:14     ` Gregory CLEMENT
2014-02-11 16:03 ` Ezequiel Garcia
2014-02-11 22:08   ` Daniel Lezcano

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=52FA20EF.30807@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).