From: David Miller <davem@davemloft.net>
To: b38611@freescale.com
Cc: shawn.guo@linaro.org, netdev@vger.kernel.org,
bhutchings@solarflare.com, stephen@networkplumber.org
Subject: Re: [PATCH net-next v1 0/3] net: fec: add Wake-on-LAN support
Date: Wed, 31 Dec 2014 13:07:27 -0500 (EST) [thread overview]
Message-ID: <20141231.130727.1660985956287926494.davem@davemloft.net> (raw)
In-Reply-To: <1419413441-3406-1-git-send-email-b38611@freescale.com>
From: Fugang Duan <b38611@freescale.com>
Date: Wed, 24 Dec 2014 17:30:38 +0800
> The patch series enable FEC Wake-on-LAN feature for i.MX6q/dl and i.MX6SX SOCs.
> FEC HW support sleep mode, when system in suspend status with FEC all clock gate
> off, magic packet can wake up system. For different SOCs, there have special SOC
> GPR register to let FEC enter sleep mode or exit sleep mode, add these to platform
> callback for driver' call.
>
> Patch#1: add WOL interface supports.
> Patch#2: add SOC special sleep of/off operations for driver's sleep callback.
> Patch#3: add magic pattern support for devicetree.
Series applied, thanks.
next prev parent reply other threads:[~2014-12-31 18:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 9:30 [PATCH net-next v1 0/3] net: fec: add Wake-on-LAN support Fugang Duan
2014-12-24 9:30 ` [PATCH net-next v1 1/3] " Fugang Duan
2014-12-24 9:30 ` [PATCH net-next v1 2/3] ARM: imx: add FEC sleep mode callback function Fugang Duan
2015-01-06 11:48 ` Shawn Guo
2015-01-07 1:41 ` fugang.duan
2015-01-07 2:33 ` Shawn Guo
2015-01-07 2:40 ` fugang.duan
2015-01-07 3:17 ` Shawn Guo
2015-01-07 12:02 ` David Miller
2015-01-07 3:44 ` Fabio Estevam
2014-12-24 9:30 ` [PATCH net-next v1 3/3] ARM: dts: imx6qdl: enable FEC magic-packet feature Fugang Duan
2014-12-31 18:07 ` David Miller [this message]
2014-12-31 19:03 ` [PATCH net-next v1 0/3] net: fec: add Wake-on-LAN support Fabio Estevam
2014-12-31 19:20 ` David Miller
2014-12-31 19:22 ` Fabio Estevam
2015-01-04 1:39 ` fugang.duan
2015-01-06 11:21 ` Shawn Guo
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=20141231.130727.1660985956287926494.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b38611@freescale.com \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stephen@networkplumber.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).