From: Jagan Teki <jagannadh.teki@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: lower the DRAM frequency of Nano Pi NEO2 to 504MHz
Date: Thu, 2 Nov 2017 18:13:12 +0530 [thread overview]
Message-ID: <CAD6G_RSut5eNiR0ZDKGv5zWf586BKro60Cdus4z07bBY2oFCAQ@mail.gmail.com> (raw)
In-Reply-To: <aef1518747690de40e52f5dc63affd46@aosc.io>
On Thu, Nov 2, 2017 at 1:57 PM, Icenowy Zheng <icenowy@aosc.io> wrote:
> 在 2017-11-02 16:25,Jagan Teki 写道:
>>
>> On Thu, Nov 2, 2017 at 9:06 AM, Icenowy Zheng <icenowy@aosc.io> wrote:
>>>
>>> The BSP of Nano Pi NEO2 provided by FriendlyARM uses 504MHz DRAM
>>> frequency, which is much lower than the current 672MHz used in
>>> mainline.
>>>
>>> Switch to use the BSP-provided frequency 504MHz for DRAM.
>>>
>>> Thanks to Thomas Kaiser, who pointed out the frequency problem.
>>>
>>> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
>>> ---
>>> configs/nanopi_neo2_defconfig | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/configs/nanopi_neo2_defconfig
>>> b/configs/nanopi_neo2_defconfig
>>> index b8e089176f..e210af4f0e 100644
>>> --- a/configs/nanopi_neo2_defconfig
>>> +++ b/configs/nanopi_neo2_defconfig
>>> @@ -1,7 +1,7 @@
>>> CONFIG_ARM=y
>>> CONFIG_ARCH_SUNXI=y
>>> CONFIG_MACH_SUN50I_H5=y
>>> -CONFIG_DRAM_CLK=672
>>> +CONFIG_DRAM_CLK=504
Did you find this abort[3] with existing master, look like autoboot corrupted
[3] https://paste.ubuntu.com/25872498/
thanks!
--
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
next prev parent reply other threads:[~2017-11-02 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 3:36 [U-Boot] [PATCH] sunxi: lower the DRAM frequency of Nano Pi NEO2 to 504MHz Icenowy Zheng
2017-11-02 8:25 ` Jagan Teki
2017-11-02 8:27 ` Icenowy Zheng
2017-11-02 12:43 ` Jagan Teki [this message]
2017-11-02 13:59 ` Maxime Ripard
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=CAD6G_RSut5eNiR0ZDKGv5zWf586BKro60Cdus4z07bBY2oFCAQ@mail.gmail.com \
--to=jagannadh.teki@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.