From: alexander.sverdlin@gmail.com (Alexander Sverdlin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: ep93xx: switch to SPARSEMEM
Date: Fri, 26 May 2017 23:28:20 +0200 [thread overview]
Message-ID: <2e8ab3d4-21ab-44e6-1b77-4db381a55fcf@gmail.com> (raw)
In-Reply-To: <c5d6d870-48f8-f6c4-1ec9-6b540d0dca98@gmail.com>
Hello Florian,
On 26/05/17 18:13, Florian Fainelli wrote:
>>> The EP93xx has four chip selects that can be used for the SDRAM memory.
>>> These chip selects are decoded to specify an address domain:
>>>
>>> SDCS3 0x00000000-0x0fffffff with Boot Option ASDO=1
>>> SDCS0 0xc0000000-0xcfffffff
>>> SDCS1 0xd0000000-0xdfffffff
>>> SDCS2 0xe0000000-x0efffffff
>>> SDCS3 0xf0000000-0xffffffff with Boot Option ASDO=0
>>>
>>> Because of the row/column/bank architecture of SDRAM, the mapping of
>>> these memories into the processor's memory space is discontiguous.
>>>
>>> Most ep93xx systems only use one of the chip selects. For these systems,
>>> ARCH_HAS_HOLES_MEMORYMODEL has worked fine to handle the discontiguous
>>> memory.
>>>
>>> But, some of the TS-72xx boards use multiple chip selects. The TS-7300 in
>>> particular uses SDCS3 (with ASDO=1) and SDCS2. On that system with
>>> ARCH_HAS_HOLES_MEMORYMODEL the SDCS2 memory does not get handled correctly
>>> and results in the system not booting.
>>>
>>> Change the EP93xx to ARCH_SPARSEMEM_ENABLE. This handles the discontiguous
>>> memory for all configurations.
>>>
>>> This has been tested on the following ep93xx platforms:
>>>
>>> EDB9307A with 64 MiB on SDCS0
>>> Vision EP9307 with 64 MiB on SDCS0
>>> TS-7300 with 64 MiB on SDCS3 (with ASDO=1) and 64 MiB on SDCS2
>>> sim.one with 64 MiB on SDCS0
>>>
>>> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
>>> Tested-by: Linus Walleij <linus.walleij@linaro.org>
>>> Cc: Russell King <linux@armlinux.org.uk>
>> Tested-by: Florian Fainelli <f.fainelli@gmail.com>
>>
>> On a TS-3700 with 32MiB of SDRAM, thanks!
>>
> OK this is weird, this patch applied against v4.11 works fine on a 32MB
> board configuration, but applied against v4.12-rc2 I now get the following:
>
> Uncompressing Linux... done, booting the kernel.
> Warning: Neither atags nor dtb found
>
> as if r2 was lost somehow.
>
> I will start a bisection to figure out if/when it started to break.
> Russell do you have an idea?
I've applied the patch to 4.12-rc2 as well (to be more precise, 1b8f2ffc of Linus's tree),
and it boots fine on EDB9302 (32MiB one chip on SDCS3). I even ran "memtester" fine, one
iteration.
So, from my PoV
Tested-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
--
Regards,
Alexander.
next prev parent reply other threads:[~2017-05-26 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:15 [PATCH 0/4] ARM: ep93xx: various updates H Hartley Sweeten
2017-02-21 18:15 ` [PATCH 1/4] ARM: ep93xx: switch to SPARSEMEM H Hartley Sweeten
2017-05-13 18:21 ` Florian Fainelli
2017-05-26 16:13 ` Florian Fainelli
2017-05-26 21:28 ` Alexander Sverdlin [this message]
2017-05-26 21:50 ` Florian Fainelli
2017-05-26 21:54 ` Hartley Sweeten
2017-05-26 22:39 ` Russell King - ARM Linux
2017-02-21 18:15 ` [PATCH 2/4] ARM: ep93xx: simone: let the mmc_spi driver handle the card detect H Hartley Sweeten
2017-05-13 18:26 ` Florian Fainelli
2017-02-21 18:15 ` [PATCH 3/4] ARM: ep93xx: tidy up TS-72xx Watchdog resources H Hartley Sweeten
2017-05-13 18:26 ` Florian Fainelli
2017-02-21 18:15 ` [PATCH 4/4] ARM: ep93xx: Add lm70 HWMON sensor to TS-72xx boards H Hartley Sweeten
2017-05-13 18:54 ` Florian Fainelli
2017-05-13 19:53 ` [PATCH 0/4] ARM: ep93xx: various updates Florian Fainelli
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=2e8ab3d4-21ab-44e6-1b77-4db381a55fcf@gmail.com \
--to=alexander.sverdlin@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).