From: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Hans Verkuil <hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
Cc: "linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: rk3288 Firefly Reload: 'reboot' doesn't work
Date: Tue, 31 Oct 2017 17:31:18 +0100 [thread overview]
Message-ID: <1729506.TeohltKTGL@diego> (raw)
In-Reply-To: <b88abf6d-d95f-3eca-91d1-65fcb749cb22-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
Hi Hans,
sorry this took a bit longer,
Am Freitag, 20. Oktober 2017, 11:06:21 CET schrieb Hans Verkuil:
> If I run 'reboot' to reboot my Firefly Reload board the last thing I see
> on the serial port is "reboot: Restarting system", but it never actually
> restarts.
>
> This is really annoying, but I have no idea where to look. Any suggestions?
I just ran reboot on my original rk3288-firefly with 4.14-rc6 and reboot worked
just fine. So it looks like at least on the kernel side it seems to check out.
Especially, as we do use the cold-reset mode on Rockchip socs so everything
should get set to its correct reset-state.
-- What bootloader do you use on the board?
I'm using mainline uboot from somewhere last year right now
[ U-Boot 2016.11-01442-g5699f71-dirty (Nov 29 2016 - 23:23:39 +0100) ]
-- What happens when you turn off cpufreq in your kernel?
I.e. one possible thing I could think of would be your cpu frequency
being low and the regulator not having the right voltage for the 600MHz
boot frequency.
But that would make me wonder, why it would work at all. I.e. while
the default for vdd_cpu is 1.0V, the lowest in the opp-table is 0.9V
which _is_ the correct voltage even for the 600MHz reset frequency.
Heiko
prev parent reply other threads:[~2017-10-31 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 9:06 rk3288 Firefly Reload: 'reboot' doesn't work Hans Verkuil
[not found] ` <b88abf6d-d95f-3eca-91d1-65fcb749cb22-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2017-10-21 14:02 ` Diego Roversi
2017-10-31 16:31 ` Heiko Stübner [this message]
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=1729506.TeohltKTGL@diego \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).