From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S5PV210: Fix on SECTION_SIZE_BITS on S5PV210/S5PC110.
Date: Thu, 08 Jul 2010 09:01:16 +0900 [thread overview]
Message-ID: <01be01cb1e30$b2d52e10$187f8a30$%kim@samsung.com> (raw)
In-Reply-To: <20100707075622.GA21830@n2100.arm.linux.org.uk>
Russell King wrote:
>
> On Wed, Jul 07, 2010 at 08:27:53AM +0900, Kukjin Kim wrote:
> > Russell King wrote:
> > > What is the spacing of chunks of memory, and minimum alignment of
those
> > > chunks in physical address space?
> >
> > Some S5PC110(MCP D-type) has only available 80MiB in a bank.
> > So the space accounts for 432MiB in a DMC0, but larger memory(256MiB +
> > 128MiB) exists in a DMC1.
>
> Ok.
>
> > As you know, the size of a section should be a power of 2 and a physical
> > address space of a section should be contiguous.
> > If a section size is greater than 16MiB, a section have a hole. So the
> > SECTION_SIZE_BITS should be 16MiB.
>
> Where is this hole? Please show it as a diagram similar to the one
> you've produced below.
>
Ok...let's suppose the size of section is 32MiB.
Physical Mem. Sections
. .
. .
. .
| | | |
0x30000000 ------------ ------------ 0x30000000
| | | offline |
| | ------------ 0x2C000000
| | | offline |
| | ------------ 0x2A000000
| none | | offline |
| | ------------ 0x28000000
| | | offline |
| | ------------ 0x26000000
0x25000000 ------------ | *online |
| | ------------ 0x24000000
| | | online |
| 80 MiB | ------------ 0x22000000
| | | online |
0x20000000 ------------ ------------ 0x20000000
In the above diagram, *section includes a 'hole' that is invalid online area
between 0x25000000 and 0x26000000.
> > > Also, what is the maximum physical address which memory can be
located?
> >
> > Following is memory map of S5PV210/S5PC110.
> >
> > 0x80000000 -------------------
> > | |
> > 0x70000000 | |
> > | |
> > 0x60000000 | DMC 1 | up to 1GiB
> > | |
> > 0x50000000 | |
> > | |
> > 0x40000000 -----------------
> > | |
> > 0x30000000 | DMC 0 | up to 512MiB
> > | |
> > 0x20000000 -------------------
>
> Right, so MAX_PHYSMEM_BITS is 31 and not 32 as you don't have memory
> at or above 0x80000000. This will immediately halve the amount of
> sparsemem supporting structures irrespective of the SECTION_SIZE_BITS
> value.
Ok..will fix it.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2010-07-08 0:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 4:36 [PATCH] ARM: S5PV210: Fix on SECTION_SIZE_BITS on S5PV210/S5PC110 Kukjin Kim
2010-07-06 5:33 ` Kyungmin Park
2010-07-06 23:49 ` Kukjin Kim
2010-07-06 7:12 ` Russell King - ARM Linux
2010-07-06 23:27 ` Kukjin Kim
2010-07-07 2:15 ` Joonyoung Shim
2010-07-07 2:28 ` Kukjin Kim
2010-07-07 4:40 ` Kyungmin Park
2010-07-07 7:56 ` Russell King - ARM Linux
2010-07-08 0:01 ` Kukjin Kim [this message]
2010-07-08 8:02 ` Russell King - ARM Linux
2010-07-08 11:01 ` Kukjin Kim
2010-07-06 10:44 ` Sergei Shtylyov
2010-07-06 23:29 ` Kukjin Kim
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='01be01cb1e30$b2d52e10$187f8a30$%kim@samsung.com' \
--to=kgene.kim@samsung.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).