netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, netdev@vger.kernel.org,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	sasha.neftin@intel.com, Naama Meir <naamax.meir@linux.intel.com>,
	Simon Horman <simon.horman@corigine.com>
Subject: Re: [PATCH net-next 2/2] e1000e: Use PME poll to circumvent unreliable ACPI wake
Date: Sun, 13 Aug 2023 12:01:25 +0300	[thread overview]
Message-ID: <20230813090125.GF7707@unreal> (raw)
In-Reply-To: <20230810175410.1964221-3-anthony.l.nguyen@intel.com>

On Thu, Aug 10, 2023 at 10:54:10AM -0700, Tony Nguyen wrote:
> From: Kai-Heng Feng <kai.heng.feng@canonical.com>
> 
> On some I219 devices, ethernet cable plugging detection only works once
> from PCI D3 state. Subsequent cable plugging does set PME bit correctly,
> but device still doesn't get woken up.
> 
> Since I219 connects to the root complex directly, it relies on platform
> firmware (ACPI) to wake it up. In this case, the GPE from _PRW only
> works for first cable plugging but fails to notify the driver for
> subsequent plugging events.
> 
> The issue was originally found on CNP, but the same issue can be found
> on ADL too. So workaround the issue by continuing use PME poll after
> first ACPI wake. As PME poll is always used, the runtime suspend
> restriction for CNP can also be removed.
> 
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> Tested-by: Naama Meir <naamax.meir@linux.intel.com>
> Acked-by: Sasha Neftin <sasha.neftin@intel.com>
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
>  drivers/net/ethernet/intel/e1000e/netdev.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>

      reply	other threads:[~2023-08-13  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 17:54 [PATCH net-next 0/2][pull request] Intel Wired LAN Driver Updates 2023-08-10 (igb, e1000e) Tony Nguyen
2023-08-10 17:54 ` [PATCH net-next 1/2] igb: Stop PTP related workqueues if aren't necessary Tony Nguyen
2023-08-13  9:01   ` Leon Romanovsky
2023-08-14 22:16     ` Tony Nguyen
2023-08-15  5:23       ` Leon Romanovsky
2023-08-15  5:46         ` Rahul Rameshbabu
2023-08-15 15:24           ` Tony Nguyen
2023-08-10 17:54 ` [PATCH net-next 2/2] e1000e: Use PME poll to circumvent unreliable ACPI wake Tony Nguyen
2023-08-13  9:01   ` Leon Romanovsky [this message]

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=20230813090125.GF7707@unreal \
    --to=leon@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=kuba@kernel.org \
    --cc=naamax.meir@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sasha.neftin@intel.com \
    --cc=simon.horman@corigine.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).