From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: Simon Kagstrom <simon.kagstrom@netinsight.net>
Cc: Dhaval Vasa <dhaval.vasa@einfochips.com>,
nico@cam.org, linux-kernel@vger.kernel.org, rabeeh@marvell.com,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH v2] [ARM] Kirkwood: Marvell OpenRD-Base board support added to v2.6.31-rc5
Date: Wed, 19 Aug 2009 15:45:20 +0200 [thread overview]
Message-ID: <20090819154520.61e33fc1@marrow.netinsight.se> (raw)
In-Reply-To: <20090819151814.7167bad0@marrow.netinsight.se>
On Wed, 19 Aug 2009 15:18:14 +0200
Simon Kagstrom <simon.kagstrom@netinsight.net> wrote:
> In my patch, I also called kirkwood_i2c_init (see below), which at
> least make the I2C bus appear (not that I've tested it very much).
And also from my patch, I added initialization of PCIe as well (taken
from rd88f6281-setup.c). So you could perhaps also add that to your
patch as well?
If needed:
Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
// Simon
diff --git a/arch/arm/mach-kirkwood/openrd_base-setup.c b/arch/arm/mach-kirkwood/openrd_base-setup.c
index f9a2166..30f84b1 100644
--- a/arch/arm/mach-kirkwood/openrd_base-setup.c
+++ b/arch/arm/mach-kirkwood/openrd_base-setup.c
@@ -71,7 +71,18 @@ static void __init openrd_base_init(void)
kirkwood_ge00_init(&openrd_base_ge00_data);
kirkwood_sata_init(&openrd_base_sata_data);
kirkwood_sdio_init(&openrd_base_mvsdio_data);
+
+ kirkwood_i2c_init();
+}
+
+static int __init openrd_base_pci_init(void)
+{
+ if (machine_is_openrd_base())
+ kirkwood_pcie_init();
+
+ return 0;
}
+subsys_initcall(openrd_base_pci_init);
MACHINE_START(OPENRD_BASE, "Marvell OpenRD Base Board")
/* Maintainer: Dhaval Vasa <dhaval.vasa@einfochips.com> */
next prev parent reply other threads:[~2009-08-19 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 12:07 [PATCH v2] [ARM] Kirkwood: Marvell OpenRD-Base board support added to v2.6.31-rc5 Dhaval Vasa
2009-08-19 13:18 ` Simon Kagstrom
2009-08-19 13:45 ` Simon Kagstrom [this message]
2009-08-19 13:49 ` Dhaval Vasa
2009-08-19 14:18 ` Simon Kagstrom
2009-08-19 14:58 ` Nicolas Pitre
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=20090819154520.61e33fc1@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.net \
--cc=dhaval.vasa@einfochips.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
--cc=rabeeh@marvell.com \
/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