From: Daniel Mack <daniel@caiaq.de>
To: Mike Rapoport <mike@compulab.co.il>
Cc: steve.glendinning@smsc.com, netdev@vger.kernel.org,
ARM Linux <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: smsc9220 with omap3
Date: Wed, 24 Jun 2009 22:21:58 +0200 [thread overview]
Message-ID: <20090624202158.GD29236@buzzloop.caiaq.de> (raw)
In-Reply-To: <4A423DA0.6010306@compulab.co.il>
On Wed, Jun 24, 2009 at 05:52:16PM +0300, Mike Rapoport wrote:
> > We're using that chip connected to a PXA300 and it works well, so I
> > wouldn't suspect the driver. Does it work from any other scenario like
> > the bootloader? And I don't know OMAP, but it might be helpful to others
> > if you posted your platform_data config.
>
> The platform_data I use is:
> static struct smsc911x_platform_config smsc911x_config = {
> .irq_polarity = SMSC911X_IRQ_POLARITY_ACTIVE_LOW,
> .irq_type = SMSC911X_IRQ_TYPE_PUSH_PULL,
> .flags = SMSC911X_USE_32BIT | SMSC911X_FORCE_INTERNAL_PHY,
> };
>
> The chip is properly detected, and if I tweak the loopback test to return 0, the
> driver does not complain any more. Moreover, it seems that RX work, at least
> ifconfig reports non-zero values for RX packets. Still, there is no even single
> packet transmitted from the smsc9220 :(
> I suspect that there's some problem with the hardware, and probably someone
> encountered similar problems and may have found a solution.
For the electrical part, there is a reference schematic from SMSC. And
on PXA, you need some dumb CMOS logic or a CPLD for proper interfacing
of the digital bus. Don't know if the latter is also necessary for OMAP.
Daniel
next prev parent reply other threads:[~2009-06-24 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 16:09 smsc9220 with omap3 Mike Rapoport
2009-06-23 22:29 ` Daniel Mack
2009-06-24 14:52 ` Mike Rapoport
2009-06-24 20:21 ` Daniel Mack [this message]
2009-06-25 5:52 ` Mike Rapoport
2009-06-26 5:53 ` Tony Lindgren
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=20090624202158.GD29236@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=mike@compulab.co.il \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@smsc.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;
as well as URLs for NNTP newsgroup(s).