From: Francois Romieu <romieu@fr.zoreil.com>
To: hayeswang <hayeswang@realtek.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 5/5] r8169: support RTL8411
Date: Mon, 9 Apr 2012 20:02:29 +0200 [thread overview]
Message-ID: <20120409180229.GA28837@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20120405083743.GB32027@electric-eye.fr.zoreil.com>
Francois Romieu <romieu@fr.zoreil.com> :
> hayeswang <hayeswang@realtek.com> :
> [...]
> > There is nothing to do for rtl_init_jumbo_ops. It is all right for keeping
> > NULL.
>
> Ok, I'll add it to the commit message for future reference.
>
> > Do I need to resend this patch?
>
> No, I'll give it a short testing and forward to David.
Rx/Tx is ok, WoL + shutdown is ok but runtime power management is not.
I tried net-next + your patches + cff4c16296754888b6fd8c886bc860a888e20257
("r8169: enable napi on resume.", required for RPM or suspend/resume after
regression in da78dbff2e05630921c551dbbc70a4b7981a8fff).
- set a 8402 and a 8411 in the same test box
- ip addr add ...
- ip link set dev ... up
- start ping from remote host
- echo auto > /sys/bus/pci/devices/.../power/control
- unplug cable
- ping stops flowing
- cat /sys/bus/pci/devices/.../power/runtime_status
-> "active"
- plug cable
-> RPM status does not change, no link, no packet, no fun.
I have tried the same with a built-in 8168b (XID 18000000).
-> RPM status changes, link recovers, packets flow.
The 8168b is a bit special, so I swapped the 8411 for a 8102e (XID 04a00000).
It resumed correctly as well.
Any idea ?
--
Ueimor
Will code drivers for food.
next prev parent reply other threads:[~2012-04-09 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1333089184-1773-5-git-send-email-hayeswang@realtek.com>
2012-03-30 6:48 ` [PATCH net-next v3 5/5] r8169: support RTL8411 Hayes Wang
2012-03-30 7:25 ` Francois Romieu
2012-04-05 6:06 ` hayeswang
2012-04-05 8:37 ` Francois Romieu
2012-04-09 18:02 ` Francois Romieu [this message]
2012-04-16 6:58 ` hayeswang
2012-04-17 11:05 ` Francois Romieu
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=20120409180229.GA28837@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=hayeswang@realtek.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