From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giuseppe CAVALLARO Subject: Re: net: stmmac: dwmac-rk: fixes for Wake-on-Lan on RK3288 Date: Thu, 16 Jun 2016 15:37:32 +0200 Message-ID: <1a9e4f56-37b0-892f-97b5-b61106e6d40b@st.com> References: <1465606839-7722-1-git-send-email-vpalatin@chromium.org> <3d278dd6-0b61-f618-b723-52f9c302c999@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: , LKML , Andrew Lunn , Douglas Anderson , =?UTF-8?Q?Heiko_St=c3=bcbner?= , Shunqian Zheng , David Miller To: Vincent Palatin Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi Vincent On 6/15/2016 7:04 PM, Vincent Palatin wrote: > On Sun, Jun 12, 2016 at 11:46 PM, Giuseppe CAVALLARO > wrote: >> On 6/11/2016 3:00 AM, Vincent Palatin wrote: >>> >>> In order to support Wake-On-Lan when using the RK3288 integrated MAC >>> (with an external RGMII PHY), we need to avoid shutting down the regulator >>> of the external PHY when the MAC is suspended as it's currently done in >>> the MAC >>> platform code. >>> As a first step, create independant callbacks for suspend/resume rather >>> than >>> re-using exit/init callbacks. So the dwmac platform driver can behave >>> differently >>> on suspend where it might skip shutting the PHY and at module unloading. >>> Then update the dwmac-rk driver to switch off the PHY regulator only if we >>> are >>> not planning to wake up from the LAN. >>> Finally add the PMT interrupt to the MAC device tree configuration, so we >>> can >>> wake up the core from it when the PHY has received the magic packet. >> >> >> IMO these could be sent for net-next and also other glue logic >> files should be reworked in order to use the new API for coherence. > > Given they will have the same set of functions for exit/init and > suspend/resume, you mean duplicating the callbacks like this : > --- a/drivers/net/ethernet/stmicro/stmmac/dwmac-sti.c > +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac-sti.c > @@ -359,6 +359,8 @@ static int sti_dwmac_probe(struct platform_device *pdev) > plat_dat->bsp_priv = dwmac; > plat_dat->init = sti_dwmac_init; > plat_dat->exit = sti_dwmac_exit; > + plat_dat->suspend = sti_dwmac_exit; > + plat_dat->resume = sti_dwmac_init; > plat_dat->fix_mac_speed = data->fix_retime_src; > > ret = sti_dwmac_init(pdev, plat_dat->bsp_priv); > > Is this anyhow useful ? I think this is mandatory otherwise you are not guaranteeing the PM stuff working on the rest of the glue-logics (not only sti); because init/exit calls won't be called anymore. So I kindly ask you to propagate the fix and send the V3. The implementation above is ok for me. peppe