From: Tom Rini <trini@kernel.crashing.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OSK5912 and CF and network broken?
Date: Wed, 15 Mar 2006 13:31:29 -0700 [thread overview]
Message-ID: <20060315203129.GC16873@smtp.west.cox.net> (raw)
In-Reply-To: <20060315194142.GD14010@atomide.com>
On Wed, Mar 15, 2006 at 11:41:42AM -0800, Tony Lindgren wrote:
> * Tom Rini <trini@kernel.crashing.org> [060315 11:28]:
> > On Wed, Mar 15, 2006 at 10:36:45AM -0800, Tony Lindgren wrote:
> > > * Tom Rini <trini@kernel.crashing.org> [060315 10:31]:
> > > > Hello. I'm trying to use current linux-omap-2.6 (source.mvista.com one)
> > > > git with the omap_osk_5912_defconfig and with U-Boot 1.1.4 release (+ 2
> > > > patches from this list). I can bring the board up just fine but when I
> > > > insert a CF device I see:
> > > > pccard: PCMCIA card inserted into slot 0
> > > > pcmcia: registering new device pcmcia0.0
> > > > NETDEV WATCHDOG: eth0: transmit timed out
> > > > ...
> > > > NETDEV WATCHDOG: eth0: transmit timed out
> > > > pccard: card ejected from slot 0
> > > >
> > > > Has anyone seen this before? Or should I just looking at the interrupt
> > > > routes? I'm assuming that the board does support me using both CF and
> > > > network at the same time. Thanks!
> > >
> > > This should not happen... It sounds like an issue with the flash bus timings.
> > > Might be worth grepping for EMIFS_CS values.
> >
> > Er, this?
> > linux-omap-2.6]$ grep -r EMIFS_CS arch/arm include/asm-arm
> > arch/arm/mach-omap1/board-osk.c:#define EMIFS_CS3_VAL (0x88013141)
> > arch/arm/mach-omap1/board-osk.c: if (EMIFS_CCS(3) != EMIFS_CS3_VAL)
> > arch/arm/mach-omap1/board-osk.c: EMIFS_CCS(3) = EMIFS_CS3_VAL;
> > include/asm-arm/arch-omap/tc.h:#define EMIFS_CS0_CONFIG (TCMIF_BASE + 0x10)
> > include/asm-arm/arch-omap/tc.h:#define EMIFS_CS1_CONFIG (TCMIF_BASE + 0x14)
> > include/asm-arm/arch-omap/tc.h:#define EMIFS_CS2_CONFIG (TCMIF_BASE + 0x18)
> > include/asm-arm/arch-omap/tc.h:#define EMIFS_CS3_CONFIG (TCMIF_BASE + 0x1c)
> > include/asm-arm/arch-omap/tc.h:#define EMIFS_CCS(n) __REG32(EMIFS_CS0_CONFIG + (4 * (n)))
>
> Yes, and then also some settings are done in drivers/pcmcia/omap_cf.c.
> Maybe omap_cf.c undoes some EMIFS_CS settings done in board-osk.c?
Yes, it does change CS2:
omap_cf: cs2, previous ccs ff80fff3 acs 00000002
omap_cf: cs2, current ccs 0004a1b3 acs 00000000
With the comment:
/* NOTE: better EMIFS setup might support more cards; but the
* TRM only shows how to affect regular flash signals, not their
* CF/PCMCIA variants...
*/
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2006-03-15 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 18:30 OSK5912 and CF and network broken? Tom Rini
2006-03-15 18:36 ` Tony Lindgren
2006-03-15 19:22 ` Tom Rini
2006-03-15 19:41 ` Tony Lindgren
2006-03-15 20:31 ` Tom Rini [this message]
2006-03-16 17:03 ` Dirk Behme
2006-03-16 17:19 ` Tom Rini
2006-03-22 15:07 ` tony
2006-03-22 15:29 ` Dirk Behme
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=20060315203129.GC16873@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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