From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: SCU registers mapping for CA9/CA5 cores
Date: Fri, 21 Jun 2013 09:13:57 +0100 [thread overview]
Message-ID: <20130621081356.GU2718@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CADApbei3QOCQRmo_oYZ_XiUVupq+4uUs7WNe6f7k_OG0LHB3=w@mail.gmail.com>
On Fri, Jun 21, 2013 at 02:11:31PM +0800, Chao Xie wrote:
> hi, Russell
> When i sbumited the patch for pxa988 which is CA9, Arnd gave me some
> suggestions of SCU mapping.
> I used static mapping in the platform file for SCU registers mapping,
> but Arnd think there should be a more general way to do it, and others
> can benefit from it. I agree with him.
>
> The following is his question for you when reply to my patch.
> "Russell, do you think using a fixmap page for the SCU makes sense?
> I'm looking for a method to consolidate the various methods of
> doing early mappings of the SCU for device tree based platforms.
> Where do you think that should be implemented?"
>
> So can you give your idea and suggestion? Thanks.
With our current fixmap region, we have 224 pages available, currently
all dedicated to kmap. kmap uses 16 pages per CPU at the moment, which
we hope is enough (it's only checked when CONFIG_DEBUG_HIGHMEM is set.)
Assuming four CPUs, that makes it 64 pages, but then we have big.LITTLE
with potentially 8 (I guess they map as separate smp_processor_id()'s)
which makes that 128. 128 is over half of the available fixmap.
If we ever saw 16 CPUs, we'd need to find a new home for fixmap. If we
needed to increase KM_TYPE_NR beyond 28, we'd be in the same situation.
We do have the 0xffff1000 - 0xffff4000 range which is currently unused.
We could put the SCU at 0xffff1000 for a single page. IOW, not a fixmap
page.
next prev parent reply other threads:[~2013-06-21 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 6:11 SCU registers mapping for CA9/CA5 cores Chao Xie
2013-06-21 8:13 ` Russell King - ARM Linux [this message]
2013-06-21 9:29 ` Arnd Bergmann
2013-06-24 1:22 ` Chao Xie
2013-06-24 9:06 ` Russell King - ARM Linux
2013-06-26 18:22 ` Arnd Bergmann
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=20130621081356.GU2718@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).