public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: mmp: bring up pxa988 with device tree support
Date: Fri, 14 Jun 2013 14:56:15 +0200	[thread overview]
Message-ID: <2766142.mFu63TyH69@wuerfel> (raw)
In-Reply-To: <CADApbeh9EJDetkvx9Sq=y58mkhU_X1oo-e_hgZqeBV9nriqTiQ@mail.gmail.com>

On Friday 14 June 2013 17:15:33 Chao Xie wrote:
> On Mon, Jun 10, 2013 at 4:35 PM, Arnd Bergmann <arnd@arndb.de> wrote:

> > I guess that is a problem we have on other platforms as well, we should
> > find a generic solution for that. It would be nice to reserve a page
> > in "fixmap" and have common code map the SCU page into that.
> >
> 
> So you mean that reserve a page in arch/arm/asm/include/fixmap.h?

Yes.

> This reserve will depend on the cpu type beacuse only A9 will have SCU part.

I think A5 and ARM11MPCore as well.

> I do not know that in fixmap, the #ifdef is acceptable or not.

Yes, it is. We don't really use fixmap on ARM for anything other than
kmap_atomic at the moment. Please have a look at the powerpc and x86
implementations.

> For the common code to map the SCU page, where do you suggest to put it?

arch/arm/kernel/smp_scu.c.

	Arnd

  reply	other threads:[~2013-06-14 12:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31  2:58 [PATCH v2] bring up pxa988 with DT Neil Zhang
2013-05-31  2:58 ` [PATCH v2] ARM: mmp: bring up pxa988 with device tree support Neil Zhang
2013-05-31 11:24   ` Arnd Bergmann
2013-06-06  2:48     ` Neil Zhang
2013-06-06 16:26       ` Arnd Bergmann
2013-06-08  1:07         ` Chao Xie
2013-06-10  8:35           ` Arnd Bergmann
2013-06-14  9:15             ` Chao Xie
2013-06-14 12:56               ` Arnd Bergmann [this message]
2013-06-17  4:17                 ` Chao Xie
2013-06-17 21:34                   ` Arnd Bergmann
2013-06-20  0:55                     ` Chao Xie
2013-06-28  2:15                       ` 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=2766142.mFu63TyH69@wuerfel \
    --to=arnd@arndb.de \
    --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