public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Przemyslaw Marczak <p.marczak@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v8 2/3] Odroid-XU3: Add support for Odroid-XU3
Date: Tue, 18 Nov 2014 14:47:16 +0100	[thread overview]
Message-ID: <546B4DE4.2060201@samsung.com> (raw)
In-Reply-To: <546B3125.9070501@samsung.com>

Hello Hyungwon,

On 11/18/2014 12:44 PM, Przemyslaw Marczak wrote:
> Hello,
>
> On 11/18/2014 02:57 AM, Hyungwon Hwang wrote:
>> Dear Przemyslaw Marczak,
>>
>>>> +/*
>>>> + * FIXME: The number of bank is actually 8. But there is no way to
>>>> reserver the
>>>> + * last 16 Mib in the last bank now. So I just excluded the last
>>>> bank
>>>> + * temporally.
>>>> + */
>>>
>>> It's not prober solution, since non-dt kernel could get wrong DRAM
>>> size. Please look at board/samsung/odroid/odroid.c - into function
>>> exynos_init().
>>>
>>> The Odroid U3 has reserved the last 1MB of the last DRAM bank.
>>
>> I agree. It is a temporary solution, and it must be fixed soon. I see
>> the exynos_init() function and adapt the method to fix the problem in
>> Odroid XU3. But it did not work. Figuring out what is wrong, I found
>> that the 2 lines of code in the exynos_init() to reserve the last 1MB
>> does not affect the behavior of Odroid U3. Even after I commented out
>> the codes, it works well. Is it a effective solution to reserve the
>> memory? Is there anything else which I am missing?
>>
>> I really appreciate for your comment. Thanks.
>>
>> Best regards,
>> Hyungwon Hwang.
>>
>
> Yes, I also checked now, that this doesn't work for your board.
>
> On Odroid U3, there was a problem in the kernel - so dram size passed to
> the kernel is decreased by 1MB. It don't make a difference for the
> U-Boot if you don't touch this memory.
>
> I can suppose that it depends on secure firmware.
>
> If you plan to fix it in the future, then it's ok. In other way it will
> require some modification of board/samsung/common/board.c dram code.
>
> You can leave it as it is, since I plan to send some patches from
> tizen.org for exynos ram init.
> And it probably will fix this issue - if dts has decreased last bank
> size with the 16MiB.
>
> Best regards,

I made some quick test:
(diff)
         for (i = 0; i < CONFIG_NR_DRAM_BANKS; i++) {
                 addr = CONFIG_SYS_SDRAM_BASE + (i * SDRAM_BANK_SIZE);
-               gd->ram_size += get_ram_size((long *)addr, SDRAM_BANK_SIZE);
+               if (i == 7)
+                       gd->ram_size += (SDRAM_BANK_SIZE - (22 << 20));
+               else
+                       gd->ram_size += SDRAM_BANK_SIZE;
         }
         return 0;

Similar in dram_init_banksize():
-               size = get_ram_size((long *)addr, SDRAM_BANK_SIZE);
+
+               if (i == 7)
+                       size = (SDRAM_BANK_SIZE - (22 << 20));
+               else
+                       size = SDRAM_BANK_SIZE;

and this works fine.
I also checked that size of the reserved area is 22MiB.

Best regards,
-- 
Przemyslaw Marczak
Samsung R&D Institute Poland
Samsung Electronics
p.marczak@samsung.com

  reply	other threads:[~2014-11-18 13:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  6:25 [U-Boot] [PATCH v8 0/3] Adds support for Exynos5422 odroid xu3 board Hyungwon Hwang
2014-11-14  6:25 ` [U-Boot] [PATCH v8 1/3] exynos5: fix GPIO information of exynos5420 Hyungwon Hwang
2014-11-17  7:45   ` Simon Glass
2014-11-17  9:51     ` Przemyslaw Marczak
2014-11-18  2:29       ` Hyungwon Hwang
2014-11-18 11:46         ` Przemyslaw Marczak
2014-11-14  6:25 ` [U-Boot] [PATCH v8 2/3] Odroid-XU3: Add support for Odroid-XU3 Hyungwon Hwang
2014-11-17 10:20   ` Przemyslaw Marczak
2014-11-18  1:57     ` Hyungwon Hwang
2014-11-18 11:44       ` Przemyslaw Marczak
2014-11-18 13:47         ` Przemyslaw Marczak [this message]
2014-11-20 12:08   ` Jaehoon Chung
2014-11-24  3:59     ` Hyungwon Hwang
2014-11-14  6:25 ` [U-Boot] [PATCH v8 3/3] Odroid-XU3: Add documentation " Hyungwon Hwang
2014-11-17  9:58   ` Przemyslaw Marczak
2014-11-18  2:38     ` Hyungwon Hwang

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=546B4DE4.2060201@samsung.com \
    --to=p.marczak@samsung.com \
    --cc=u-boot@lists.denx.de \
    /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