mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, opendmb@gmail.com,
	bcm-kernel-feedback-list@broadcom.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: bcmgenet: Support wake-up from s2idle
Date: Mon, 20 Feb 2023 11:50:16 +0000	[thread overview]
Message-ID: <167689381651.15107.14601343840976421497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230217183415.3300158-1-f.fainelli@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 17 Feb 2023 10:34:14 -0800 you wrote:
> When we suspend into s2idle we also need to enable the interrupt line
> that generates the MPD and HFB interrupts towards the host CPU interrupt
> controller (typically the ARM GIC or MIPS L1) to make it exit s2idle.
> 
> When we suspend into other modes such as "standby" or "mem" we engage a
> power management state machine which will gate off the CPU L1 controller
> (priv->irq0) and ungate the side band wake-up interrupt (priv->wol_irq).
> It is safe to have both enabled as wake-up sources because they are
> mutually exclusive given any suspend mode.
> 
> [...]

Here is the summary with links:
  - [net-next] net: bcmgenet: Support wake-up from s2idle
    https://git.kernel.org/netdev/net-next/c/3fcdf2dfefb6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-02-20 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 18:34 Florian Fainelli
2023-02-20 11:50 ` patchwork-bot+netdevbpf [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=167689381651.15107.14601343840976421497.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=opendmb@gmail.com \
    --cc=pabeni@redhat.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
all inboxes | Powered by JetHome®