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 questions on rk3399 platfrom
Date: Tue, 23 May 2017 16:36:58 +0800	[thread overview]
Message-ID: <0904ca87-0e4b-aa9c-a982-16b3758956a8@rock-chips.com> (raw)
In-Reply-To: <CAPnjgZ2bDcoti7nTNJ-DgJd8L65NvaB1wHnXDHys1tVWbPSrUA@mail.gmail.com>

Hi Ziyuan, Simon,


On 05/20/2017 10:29 AM, Simon Glass wrote:
> Hi Ziyuan,
>
> On 8 May 2017 at 01:01, Ziyuan <xzy.xu@rock-chips.com> wrote:
>> hi simon,
>>
>> I need to achieve emmc_phy physical address in driver, so that I can
>> configure phy in different scenarios (phy register address should be
>> 0xff77f780). see below:
>>      sdhci: sdhci at fe330000 {
>>
>>          phys = <&emmc_phy>;
>>          phy-names = "phy_arasan";
>>
>>      };
>>
>>      grf: syscon at ff770000 {
>>          reg = <0x0 0xff770000 0x0 0x10000>;
>>
>>          emmc_phy: phy at f780 {
>>              compatible = "rockchip,rk3399-emmc-phy";
>>              reg = <0xf780 0x24>;
>>              #phy-cells = <0>;
>>              status = "disabled";
>>          };
>>      };
>>
>>   AKA, I can't use libfdt if OF_PLATDATA is enabled,  so how to get it?
>>
> At present this is not supported. I'm not quite sure how to support
> it, or at least the best way. Do you have ideas on what the C
> structure should be for this?

     I don't know how much operation for grf access is needed in SPL,

but I think driver in SPL should be simple, and OF_PLATDATA is also for

reduce memory size requirement in SPL. If operation is not much, can we

just use the GRF base address directly when OF_PLATDATA enabled? just

like other GRF access in SPL on different board files.


Thanks,
- Kever
>
> Regards,
> Simon
>

  reply	other threads:[~2017-05-23  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08  7:01 [U-Boot] OF_PLATDATA questions on rk3399 platfrom Ziyuan
2017-05-20  2:29 ` Simon Glass
2017-05-23  8:36   ` Kever Yang [this message]
2017-06-21  3:29     ` 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=0904ca87-0e4b-aa9c-a982-16b3758956a8@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.