diff options
| author | Claudiu Manoil <claudiu.manoil@freescale.com> | 2015-07-31 18:38:33 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-08-01 01:41:49 +0300 |
| commit | b0734b6dc895258b74c6e7a441cb47b6b0ba3465 (patch) | |
| tree | 29c4b47469d63ffbea013c01167a7602ecc78bb7 /crypto/rng.c | |
| parent | 614b42426cc3483e8d5bc68a158c2dd47dc831d0 (diff) | |
| download | linux-b0734b6dc895258b74c6e7a441cb47b6b0ba3465.tar.xz | |
gianfar: Enable device wakeup when appropriate
The wol_en flag is 0 by default anyway, and we have the
following inconsistency: a MAGIC packet wol capable eth
interface is registered as a wake-up source but unable
to wake-up the system as wol_en is 0 (wake-on flag set to 'd').
Calling set_wakeup_enable() at netdev open is just redundant
because wol_en is 0 by default.
Let only ethtool call set_wakeup_enable() for now.
The bflock is obviously obsoleted, its utility has been corroded
over time. The bitfield flags used today in gianfar are accessed
only on the init/ config path, with no real possibility of
concurrency - nothing that would justify smth. like bflock.
Signed-off-by: Claudiu Manoil <claudiu.manoil@freescale.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto/rng.c')
0 files changed, 0 insertions, 0 deletions