linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: xiechao.mail@gmail.com (Chao Xie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/7] arm: mmp&dove: modify tauros2_init call
Date: Tue, 31 Jul 2012 15:09:12 +0800	[thread overview]
Message-ID: <CADApbehptEE++NoxBmTuPmbWY7q9Je_vXPxMv3Sq86_f_SpBCg@mail.gmail.com> (raw)
In-Reply-To: <20120731070153.GA13777@lunn.ch>

On Tue, Jul 31, 2012 at 3:01 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> Hi Chao
>
> When making changes to Dove, or any other Orion system, please could
> you CC: the orion maintainers:
>
> ARM/Marvell Dove/Kirkwood/MV78xx0/Orion SOC support
> M:      Jason Cooper <jason@lakedaemon.net>
> M:      Andrew Lunn <andrew@lunn.ch>
> L:      linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
> S:      Maintained
> F:      arch/arm/mach-dove/
> F:      arch/arm/mach-kirkwood/
> F:      arch/arm/mach-mv78xx0/
> F:      arch/arm/mach-orion5x/
> F:      arch/arm/plat-orion/
>
> Does this also affect Armada 370 and Armada XP SOC? I've no idea what
> cache it uses.
>
> Thanks
>         Andrew
It will impact Armada 370. The patch will make the user has choice to
enable extra features of tauros2
I have searched the code, only dove will use tauros2_init, and the
tauros2 default has its extra features off, so i directly pass 0x0 for
dove

  reply	other threads:[~2012-07-31  7:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  7:01 [PATCH 6/7] arm: mmp&dove: modify tauros2_init call Andrew Lunn
2012-07-31  7:09 ` Chao Xie [this message]
2012-07-31  7:17   ` Andrew Lunn
2012-07-31  7:18   ` Gregory CLEMENT
2012-08-04  4:13     ` Haojian Zhuang
  -- strict thread matches above, loose matches on Subject: below --
2012-07-31  6:13 [PATCH 1/7] ARM: pxa: support CKENC in clk_enable Chao Xie
2012-07-31  6:13 ` [PATCH 6/7] arm: mmp&dove: modify tauros2_init call Chao Xie

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=CADApbehptEE++NoxBmTuPmbWY7q9Je_vXPxMv3Sq86_f_SpBCg@mail.gmail.com \
    --to=xiechao.mail@gmail.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).