From: Heiko Stuebner <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Rockchip RK3288 u-boot with mainline kernel
Date: Sat, 03 Dec 2016 22:24:56 +0100 [thread overview]
Message-ID: <98726149.SLlGisoKlg@phil> (raw)
In-Reply-To: <0cac6a894a714faf7da9c50d0b342bec.squirrel@webmail.efn.org>
Hi Rick,
Am Samstag, 3. Dezember 2016, 10:07:25 CET schrieb Rick Bronson:
> Thanks very much for the link. I got it, went to the branch,
> applied my patches from main denx u-boot and got it to work!
>
> The only odd thing is, I have to do this:
>
> regulator dev vcc_lan
> regulator enable
>
> Or else I can't use the networking.
>
> When I boot up I see:
>
> => regulator status
> Name Enabled uV mA Mode
> ...
> vcc_lan disabled - - -
>
> I've studied all of the various rk3288*.dts* examples but have no
> idea why the vcc_lan does not start up upon boot. My dtsi file is
> below. Thanks for any help.
Firefly and Rock2 use an act8846 as pmic while your board seems to use the
rk808. The switch used to control your vcc_lan is most likely off on boot
while the regulator used on firefly etc is most likely simply on on boot.
I don't know if the devicemanager-part of uboot actually handles such
regulator-supplies at all.
Heiko
next prev parent reply other threads:[~2016-12-03 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 18:07 [U-Boot] Rockchip RK3288 u-boot with mainline kernel Rick Bronson
2016-12-03 21:24 ` Heiko Stuebner [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-06 0:56 Rick Bronson
2016-12-07 3:48 ` Simon Glass
2016-12-01 19:00 Rick Bronson
2016-12-01 21:01 ` Heiko Stuebner
2016-11-29 22:50 Rick Bronson
2016-11-29 18:22 Rick Bronson
2016-11-29 21:40 ` Simon Glass
2016-11-29 22:11 ` Heiko Stübner
2016-11-25 18:20 Rick Bronson
2016-11-28 22:09 ` Simon Glass
2016-11-29 10:20 ` Heiko Stübner
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=98726149.SLlGisoKlg@phil \
--to=heiko@sntech.de \
--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