public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: mvebu: fixes and improvements for 375 support
Date: Thu, 8 May 2014 12:54:30 -0400	[thread overview]
Message-ID: <20140508165430.GI12708@titan.lakedaemon.net> (raw)
In-Reply-To: <1399302326-6917-1-git-send-email-thomas.petazzoni@free-electrons.com>

On Mon, May 05, 2014 at 05:05:21PM +0200, Thomas Petazzoni wrote:
> Hello Jason,
> 
> Here are five patches making fixes and improvements to the Armada 375
> support. They are related to the fact that we now have access to
> Armada 375 A0 boards (however, Ezequiel still only has access to a Z1
> platform, so we would like to keep Z1 support for now).
> 
>  * Patch 1 is really a fix. It fixes the thermal related quirk that
>    was added by Ezequiel, to make sure it really works on A0 revision.
> 
>  * Patch 2 to 5 make the SMP and coherency workarounds conditional on
>    the Armada 375 Z1. The condition on SMP is really mandatory to get
>    SMP working on A0. For coherency, the WA could be used on A0, but
>    it is useless and hurt performance.
> 
> The series is based on your mvebu/soc branch.
> 
> Changes since v1:
> 
>  * Made the dev and rev variable local to the appropriate if() block
>    in PATCH 5.
> 
>  * Re-added the "Booting CPU" message in PATCH 4, which was
>    mistakently removed in v1.
> 
>  * Extended the git commit message of PATCH 4 to explain why we're
>    moving things from ->smp_prepare_cpus() to ->smp_boot_secondary().
> 
>  * Added Ezequiel's Acked-by on PATCH 1.
> 
> Thanks,
> 
> Thomas
> 
> Thomas Petazzoni (5):
>   ARM: mvebu: fix thermal quirk SoC revision check
>   ARM: mvebu: initialize mvebu-soc-id earlier
>   ARM: mvebu: add Armada 375 A0 revision definition
>   ARM: mvebu: conditionalize Armada 375 SMP workaround
>   ARM: mvebu: conditionalize Armada 375 coherency workaround
> 
>  arch/arm/mach-mvebu/board-v7.c     |  2 +-
>  arch/arm/mach-mvebu/coherency.c    | 10 ++++++++--
>  arch/arm/mach-mvebu/mvebu-soc-id.c |  2 +-
>  arch/arm/mach-mvebu/mvebu-soc-id.h |  1 +
>  arch/arm/mach-mvebu/platsmp-a9.c   | 20 +++++++++++---------
>  5 files changed, 22 insertions(+), 13 deletions(-)

Whole series applied to mvebu/soc

I've not Cc'd stable for the first patch since the problem is only in
mvebu/soc atm. :)

thx,

Jason.

      parent reply	other threads:[~2014-05-08 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 15:05 [PATCH v2 0/5] ARM: mvebu: fixes and improvements for 375 support Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 1/5] ARM: mvebu: fix thermal quirk SoC revision check Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 2/5] ARM: mvebu: initialize mvebu-soc-id earlier Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 3/5] ARM: mvebu: add Armada 375 A0 revision definition Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 4/5] ARM: mvebu: conditionalize Armada 375 SMP workaround Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 5/5] ARM: mvebu: conditionalize Armada 375 coherency workaround Thomas Petazzoni
2014-05-05 15:36 ` [PATCH v2 0/5] ARM: mvebu: fixes and improvements for 375 support Jason Cooper
2014-05-05 16:05   ` Thomas Petazzoni
2014-05-05 16:09     ` Jason Cooper
2014-05-08 16:54 ` Jason Cooper [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=20140508165430.GI12708@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --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