From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 00214C07E96 for ; Fri, 9 Jul 2021 01:30:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CED5361467 for ; Fri, 9 Jul 2021 01:30:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230180AbhGIBdX (ORCPT ); Thu, 8 Jul 2021 21:33:23 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:47014 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229953AbhGIBdX (ORCPT ); Thu, 8 Jul 2021 21:33:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=iR/91e9r/pV24uz7F/ZCZMYq8GdTcOgKPN8iEDrQRb8=; b=ljJbRil4n+6JOT76mK3vtCkveF C2LNsuSXdXSMa33p02M3bMCMeg7pG/fthTEeE0tLgoSIPmnM+KjC9vIP5nGaP4+UxR0hsAGWhZzK/ tcxWx0uksOw18Anq1E0EHrtFWfzMUKLu8F8p7+vd39w3GejF5pVaIuxOzD/A6sXzSaiE=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1m1fLS-00ChH2-OR; Fri, 09 Jul 2021 03:30:22 +0200 Date: Fri, 9 Jul 2021 03:30:22 +0200 From: Andrew Lunn To: Florian Fainelli Cc: "Ismail, Mohammad Athari" , Heiner Kallweit , "David S . Miller" , Russell King , Jakub Kicinski , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH net] net: phy: reconfigure PHY WOL in resume if WOL option still enabled Message-ID: References: <20210708004253.6863-1-mohammad.athari.ismail@intel.com> <4e159b98-ec02-33b7-862a-0e35832c3a5f@gmail.com> <9871a015-bcfb-0bdb-c481-5e8f2356e5ba@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Ah yes you are right, we just skip resume in that case. OK let me think > about it some more. The point here is, it is an interrupt, from the perspective of the PHY hardware and its driver. But the interrupt handler is never being called because the interrupt output from the chip is not causing an actual interrupt. Fix that, and your problem goes away. Or you need to add a whole new mechanism that you are using the interrupt hardware in the PHY some something else than an actual interrupt. Andrew