All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] of-platdata address map decode for 64-bits
Date: Sun, 05 Feb 2017 08:30:53 +0800	[thread overview]
Message-ID: <5896723D.3040909@rock-chips.com> (raw)
In-Reply-To: <CAPnjgZ1ukVVQ1Zg_M14hkwfs2qc5y=Ja5NMSYAhuWL3vxp+JzA@mail.gmail.com>

Hi Simon,

     For rk3399, the data for sdram driver in dts is big, I don't want 
to do the copy for it,
so I think use of-platdata is a good method, and for image size, its 
smaller, then it's sooner to load.

Thanks,
- Kever
On 01/26/2017 10:22 PM, Simon Glass wrote:
> Hi Kever,
>
> On 17 January 2017 at 23:37, Kever Yang <kever.yang@rock-chips.com> wrote:
>> Hi Simon,
>>
>>      For my rk3399(64bit) dts, the address is described as below:
>> #address-cells = <2>;
>> reg = <0x0 0xfe320000 0x0 0x4000>;
>>
>> not like 32-bit soc which reg address describe like:
>> reg = <0xfe320000 0x4000>;
>>
>>      There should have some update for this dts decode, right?
>> like:
>> map_sysmem()
>> regmap_init_mem_platdata()
>>
>>      Do you have a idea to update all these kind of function call?
>> It will be very great if you can send a patch for it.
>>
>> Thanks,
>> - Kever
>>
> Yes I think so.
>
> But first I'd like to understand why we need to use of-platdata on
> this very modern SoC. Can you tell me the maximum SPL size you can
> support on this SoC? I thought you had removed the 30KB limit?
>
> Using of-platdata only saves 3-4KB.
>
> Regards,
> Simon
>
>
>

  reply	other threads:[~2017-02-05  0:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  6:37 [U-Boot] of-platdata address map decode for 64-bits Kever Yang
2017-01-26 14:22 ` Simon Glass
2017-02-05  0:30   ` Kever Yang [this message]
2017-02-08  5:10     ` Simon Glass
2017-02-13  8:13       ` Kever Yang
2017-02-14  5:31         ` Simon Glass
2017-02-21 13:08           ` Kever Yang
2017-02-22  4:00             ` Simon Glass

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=5896723D.3040909@rock-chips.com \
    --to=kever.yang@rock-chips.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.