From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 3/9] arm: mach-mvebu: add source files
Date: Mon, 2 Jul 2012 13:36:27 +0200 [thread overview]
Message-ID: <20120702133627.4f7baec0@skate> (raw)
In-Reply-To: <20120627153652.GE29702@lunn.ch>
Le Wed, 27 Jun 2012 17:36:52 +0200,
Andrew Lunn <andrew@lunn.ch> a ?crit :
> > +void mvebu_restart(char mode, const char *cmd)
> > +{
> > + if (!system_controller_base) {
> > + pr_warn("Cannot restart, system-controller not available\n");
>
> Does pr_warn() get shown by default? I would of probably gone for
> BUG_ON() or WARN_ON(), to make it clearer what has happened. It may
> not be a kernel bug, but a DT description bug, but it still a bug...
>From my testing, pr_warn() messages are shown by default, but I've
turned this message into a pr_err() to be sure, and we've expanded the
message a bit to make it clear that the problem comes from the DT.
> I tested this on a Kirkwood QNAP with DT property:
>
> system-controller at 20000 {
> compatible = "marvell,orion-system-controller";
> reg = <0x20000 0x1000>;
> };
>
> and it works. So:
>
> Tested-by: Andrew Lunn <andrew@lunn.ch>
>
> However Orion5x has a slightly different variant, so i would like to
> test it on that SoC as well. However, we don't have DT on Orion5x yet,
> so i need to simulate it.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-02 11:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 13:54 [PATCH v5] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Gregory Clement
2012-06-27 13:54 ` [PATCH v5 1/9] clocksource: time-armada-370-xp: Marvell Armada 370/XP SoC timer driver Gregory Clement
2012-06-27 13:54 ` [PATCH v5 2/9] arm: mach-mvebu: add header Gregory Clement
2012-06-27 13:54 ` [PATCH v5 3/9] arm: mach-mvebu: add source files Gregory Clement
2012-06-27 15:36 ` Andrew Lunn
2012-06-28 18:07 ` Nicolas Pitre
2012-07-02 11:36 ` Thomas Petazzoni [this message]
2012-06-27 13:54 ` [PATCH v5 4/9] arm: mach-mvebu: add support for Armada 370 and Armada XP with DT Gregory Clement
2012-06-27 16:11 ` Ben Dooks
2012-07-02 11:37 ` Thomas Petazzoni
2012-06-27 13:54 ` [PATCH v5 5/9] arm: mach-mvebu: add documentation for new device tree bindings Gregory Clement
2012-06-27 13:54 ` [PATCH v5 6/9] arm: mach-mvebu: add defconfig Gregory Clement
2012-06-27 13:54 ` [PATCH v5 7/9] arm: mach-mvebu: add compilation/configuration change Gregory Clement
2012-06-27 13:54 ` [PATCH v5 8/9] arm: mach-mvebu: add entry to MAINTAINERS Gregory Clement
2012-06-27 13:54 ` [PATCH v5 9/9] ARM: mvebu: MPIC: read number of interrupts from control register Gregory Clement
2012-06-27 15:54 ` [PATCH v5] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Ben Dooks
2012-07-02 8:30 ` Thomas Petazzoni
2012-07-02 9:19 ` Ben Dooks
2012-07-02 9:19 ` Thomas Petazzoni
2012-07-02 9:25 ` Ben Dooks
2012-07-02 9:26 ` Thomas Petazzoni
2012-06-27 16:26 ` review comments Ben Dooks
2012-06-27 16:26 ` [PATCH 1/3] arm: mach-mvebu: fixup style error in system-controller Ben Dooks
2012-06-27 16:26 ` [PATCH 2/3] arm: mach-mvebu: check result of of_match_node() Ben Dooks
2012-06-27 16:26 ` [PATCH 3/3] arm: mach-mvebu: system-controller only registers restart if device exists Ben Dooks
2012-06-27 19:19 ` Russell King - ARM Linux
2012-06-28 9:23 ` Ben Dooks
2012-06-28 10:17 ` Russell King - ARM Linux
2012-07-02 11:35 ` review comments Thomas Petazzoni
2012-06-28 12:10 ` [PATCH v5] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Lior Amsalem
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=20120702133627.4f7baec0@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 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).