From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Simon Horman <horms+renesas@verge.net.au>,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCHv2 0/5] sh_eth: add wake-on-lan support via magic packet
Date: Mon, 12 Dec 2016 17:09:26 +0100 [thread overview]
Message-ID: <20161212160931.6478-1-niklas.soderlund+renesas@ragnatech.se> (raw)
Hi,
This series adds support for Wake-on-Lan using Magic Packet for a few
models of the sh_eth driver. Patch 1/5 adds generic support to control
and support WoL while patches 2/5 - 5/5 enable different models.
Changes since v1.
- Spit generic WoL functionality and device enablement to different
patches.
- Enable more devices then Gen2 after feedback from Geert and
datasheets.
- Do not set mdp->irq_enabled = false and remove specific MagicPacket
interrupt clearing, instead let sh_eth_error() clear the interrupt as
for other EMAC interrupts, thanks Sergei for the suggestion.
- Use the original return logic in sh_eth_resume().
- Moved sh_eth_private variable *clk to top of data structure to avoid
possible gaps due to alignment restrictions.
- Make wol_enabled in sh_eth_private part of the already existing
bitfield instead of a bool.
- Do not initiate mdp->wol_enabled to 0, the struct is kzalloc'ed so
it's already set to 0.
Niklas Söderlund (5):
sh_eth: add generic wake-on-lan support via magic packet
sh_eth: enable wake-on-lan for Gen2 devices
sh_eth: enable wake-on-lan for r8a7740/armadillo
sh_eth: enable wake-on-lan for sh7743
sh_eth: enable wake-on-lan for sh7763
drivers/net/ethernet/renesas/sh_eth.c | 121 +++++++++++++++++++++++++++++++---
drivers/net/ethernet/renesas/sh_eth.h | 3 +
2 files changed, 114 insertions(+), 10 deletions(-)
--
2.10.2
next reply other threads:[~2016-12-12 16:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 16:09 Niklas Söderlund [this message]
2016-12-12 16:09 ` [PATCHv2 1/5] sh_eth: add generic wake-on-lan support via magic packet Niklas Söderlund
2016-12-13 13:03 ` Geert Uytterhoeven
2016-12-13 16:27 ` Niklas Söderlund
2016-12-17 21:50 ` Sergei Shtylyov
2016-12-19 16:41 ` Niklas Söderlund
2016-12-19 16:56 ` Sergei Shtylyov
2016-12-18 20:26 ` Sergei Shtylyov
2016-12-19 16:39 ` Niklas Söderlund
2016-12-19 17:11 ` Geert Uytterhoeven
2016-12-24 21:53 ` Sergei Shtylyov
2016-12-12 16:09 ` [PATCHv2 2/5] sh_eth: enable wake-on-lan for Gen2 devices Niklas Söderlund
2016-12-13 12:52 ` Geert Uytterhoeven
2016-12-14 13:37 ` Sergei Shtylyov
2016-12-17 21:52 ` Sergei Shtylyov
2016-12-12 16:09 ` [PATCHv2 3/5] sh_eth: enable wake-on-lan for r8a7740/armadillo Niklas Söderlund
2016-12-13 12:51 ` Geert Uytterhoeven
2016-12-12 16:09 ` [PATCHv2 4/5] sh_eth: enable wake-on-lan for sh7743 Niklas Söderlund
2016-12-13 10:59 ` Geert Uytterhoeven
2016-12-12 16:09 ` [PATCHv2 5/5] sh_eth: enable wake-on-lan for sh7763 Niklas Söderlund
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=20161212160931.6478-1-niklas.soderlund+renesas@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).