All of lore.kernel.org
 help / color / mirror / Atom feed
From: simon.guinot@sequanux.org (Simon Guinot)
To: linux-arm-kernel@lists.infradead.org
Subject: Reboot hangs on Kirkwood ns2 boards with 3.8-rc2
Date: Sun, 6 Jan 2013 04:34:55 +0100	[thread overview]
Message-ID: <20130106033455.GH1357@kw.sim.vm.gnt> (raw)

Hi Andrew and Jason,

While testing 3.8-rc2 on the ns2 boards (DT based), I noticed that
reboot is not working. After issuing a reboot, the kernel hangs. No
error messages are displayed. Moreover, on my non-DT Kirkwood boards,
reboot is working as expected.

Am I the only one to experiment this issue ?

After some painful investigations, I found out that my problem may be
related with the device tree binding addition to the driver ehci-orion.
I still don't understand exactly why, but if I add the "clocks" property
to the ehci node, reboot works.

diff --git a/arch/arm/boot/dts/kirkwood.dtsi
b/arch/arm/boot/dts/kirkwood.dtsi
index 7735cee..110d6cb 100644
--- a/arch/arm/boot/dts/kirkwood.dtsi
+++ b/arch/arm/boot/dts/kirkwood.dtsi
@@ -144,6 +144,7 @@
                        compatible = "marvell,orion-ehci";
                        reg = <0x50000 0x1000>;
                        interrupts = <19>;
+                       clocks = <&gate_clk 3>;
                        status = "okay";
                };

Do you have any idea ?

Regards,

Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130106/d6f72a2a/attachment.sig>

             reply	other threads:[~2013-01-06  3:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06  3:34 Simon Guinot [this message]
2013-01-06  8:35 ` Reboot hangs on Kirkwood ns2 boards with 3.8-rc2 Andrew Lunn
2013-01-07 15:09   ` Simon Guinot
2013-01-07 15:25     ` Andrew Lunn
2013-01-07 15:32       ` Simon Guinot

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=20130106033455.GH1357@kw.sim.vm.gnt \
    --to=simon.guinot@sequanux.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.