From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: kda@linux-powerpc.org, venza@brownhat.org, B38611@freescale.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v3] sis900: Fix the tx queue timeout issue
Date: Fri, 02 Aug 2013 15:04:00 -0700 (PDT) [thread overview]
Message-ID: <20130802.150400.1854139334376781614.davem@davemloft.net> (raw)
In-Reply-To: <1375471135.32254.15.camel@deadeye.wl.decadent.org.uk>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 2 Aug 2013 21:18:55 +0200
> This looks reasonable. It looks like link changes now work like this:
>
> 1. When sis900_timer() detects link-down, it calls netif_carrier_off()
> but does not clear autong_complete.
> 2. When sis900_timer() detects link-up, it calls sis900_check_mode()
> which restarts autonegotiation and clears autong_complete.
> 3. sis900_timer() will now call sis900_read_mode(). When that detects
> link-up, it sets autong_complete and calls netif_carrier_on().
>
> This patch has moved the call to netif_carrier_on() from step 2 to step
> 3. However, I don't understand why autonegotiation is restarted in step
> 2. When autonegotiation is enabled, the PHY should not indicate link-up
> until it has completed. Perhaps this is a necessary workaround for a
> hardware bug. Otherwise it's a waste of time.
Agreed, if the PHY was configured to use autonegotiation, getting a link
up event afterwards implies that autonegotiation is complete.
In any event, I'm going to apply this patch anyways because it is far and
above a significant move forward.
next prev parent reply other threads:[~2013-08-02 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 9:50 [PATCH v3] sis900: Fix the tx queue timeout issue Denis Kirjanov
2013-08-02 19:18 ` Ben Hutchings
2013-08-02 22:04 ` David Miller [this message]
2013-08-03 8:00 ` Denis Kirjanov
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=20130802.150400.1854139334376781614.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=B38611@freescale.com \
--cc=bhutchings@solarflare.com \
--cc=kda@linux-powerpc.org \
--cc=netdev@vger.kernel.org \
--cc=venza@brownhat.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