From: andy@warmcat.com (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] smdk6410-comment-ethernet-prerequisites.patch
Date: Tue, 29 Dec 2009 14:40:43 +0000 [thread overview]
Message-ID: <20091229144042.15524.35906.stgit@hit-nxdomain.opendns.com> (raw)
In-Reply-To: <20091229143756.15524.25160.stgit@hit-nxdomain.opendns.com>
LAN9115 Ethernet only works on SMDK6410 if certain switches
are set in specific ways. Document the requirement.
Signed-off-by: Andy Green <andy@warmcat.com>
---
arch/arm/mach-s3c6410/mach-smdk6410.c | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-s3c6410/mach-smdk6410.c b/arch/arm/mach-s3c6410/mach-smdk6410.c
index d613932..c70661d 100644
--- a/arch/arm/mach-s3c6410/mach-smdk6410.c
+++ b/arch/arm/mach-s3c6410/mach-smdk6410.c
@@ -155,6 +155,16 @@ static struct s3c_fb_platdata smdk6410_lcd_pdata __initdata = {
.vidcon1 = VIDCON1_INV_HSYNC | VIDCON1_INV_VSYNC,
};
+/*
+ * Configuring Ethernet on SMDK6410
+ *
+ * Both CS8900A and LAN9115 chips share one chip select mediated by CFG6.
+ * The constant address below corresponds to nCS1
+ *
+ * 1) Set CFGB2 p3 ON others off, no other CFGB selects "ethernet"
+ * 2) CFG6 needs to be switched to "LAN9115" side
+ */
+
static struct resource smdk6410_smsc911x_resources[] = {
[0] = {
.start = S3C64XX_PA_XM0CSN1,
next prev parent reply other threads:[~2009-12-29 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 14:40 [PATCH 0/4] Add s3c64xx SROM support and setup SMDK nCS1 for Ethernet Andy Green
2009-12-29 14:40 ` [PATCH 1/4] s3c64xx-introduce-srom-registers.patch Andy Green
2009-12-29 14:40 ` [PATCH 2/4] s3c64xx-add-srom-physical-virtual-mapping.patch Andy Green
2009-12-29 14:40 ` [PATCH 3/4] smdk6410-add-chipselect-setup.patch Andy Green
2009-12-29 14:40 ` Andy Green [this message]
2010-01-04 2:55 ` [PATCH 0/4] Add s3c64xx SROM support and setup SMDK nCS1 for Ethernet Ben Dooks
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=20091229144042.15524.35906.stgit@hit-nxdomain.opendns.com \
--to=andy@warmcat.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).