netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: netdev@vger.kernel.org, Enric Balletbo i Serra <eballetbo@iseebcn.com>
Subject: Re: [BUG] SIOCSIFFLAGS returns -EIO on SMSC LAN911x
Date: Fri, 30 Dec 2011 11:56:13 +0100	[thread overview]
Message-ID: <1325242573.13595.71.camel@deadeye> (raw)
In-Reply-To: <CAAwP0s37E=9J-KR397snkvq=idrc7nmELDJKrm33reeK84wJYQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]

On Fri, 2011-12-30 at 10:44 +0100, Javier Martinez Canillas wrote:
> Hello,
> 
> We have an issue with the SMSC LAN911x driver with today linux-2.6 [1]
> executing on an IGEPv2 [2] board using omap2plus_defconfig.
> 
> When I try to bring up the network interface, the ioctl set interface
> flags command (SIOCSIFFLAGS)  fails returning -EIO:
[...]
> By doing a git bisect we found that this strange behavior exists when
> the Kconfig tristate compilation condition SMSC_PHY has the value yes
> to be compiled built-in:
> 
> SMSC_PHY=y
> 
> If this config symbol has the value module (m) or not build at all,
> then bringing up the network interface never fails.

So the PHY driver is doing something that interferes with soft reset.

The data sheet for this part
<http://www.smsc.com/media/Downloads_Public/Data_Sheets/9221.pdf> says
that soft reset does not work if the PHY is in certain states.  Also, it
doesn't seem to specify a maximum time for soft reset to complete,
though it does say that PHY reset takes 100 us.

> Did anyone have the same problem?
> 
> The problem is really strange to me, especially since we are sure that
> all the requirements to software reset the device are meet in both
> cases (with SMSC_PHY compiled built-in and without it)

I don't know about that.  smsc_phy_config_init() attempts to enable
power-saving on the PHY, but it is writing to a bit that is reserved
according to the data sheet for the combined MAC/PHY chip.  You might
want to try reverting:

commit 698244ace8b63896565022143ab19f141bc48993
Author: Giuseppe Cavallaro <peppe.cavallaro@st.com>
Date:   Wed Jan 6 20:35:14 2010 -0800

    phy: SMSC device Energy Detect power-down mode

Ben.

> [1]: HEAD on commit 371de6e4e0042adf4f9b54c414154f57414ddd37 drm/i915:
> Disable RC6 on Sandybridge by default
> [2]: https://wiki.linaro.org/Boards/Igep
> 
> Thank you and best regards,
> 

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2011-12-30 10:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30  9:44 [BUG] SIOCSIFFLAGS returns -EIO on SMSC LAN911x Javier Martinez Canillas
2011-12-30 10:56 ` Ben Hutchings [this message]
2011-12-30 12:04   ` Javier Martinez Canillas
2011-12-30 12:58   ` Javier Martinez Canillas
2011-12-30 13:15     ` Ben Hutchings
2012-01-02 18:37       ` Javier Martinez Canillas
2012-01-02 19:45         ` Ben Hutchings
2012-01-03  7:44           ` Javier Martinez Canillas

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=1325242573.13595.71.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=eballetbo@iseebcn.com \
    --cc=martinez.javier@gmail.com \
    --cc=netdev@vger.kernel.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).