netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nicolas.ferre@microchip.com
Cc: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
	netdev@vger.kernel.org, claudiu.beznea@microchip.com,
	harini.katakam@xilinx.com, f.fainelli@gmail.com,
	linux-kernel@vger.kernel.org, alexandre.belloni@bootlin.com,
	antoine.tenart@bootlin.com
Subject: Re: [PATCH v7 0/2] net: macb: Wake-on-Lan magic packet GEM and MACB handling
Date: Mon, 20 Jul 2020 17:02:38 -0700 (PDT)	[thread overview]
Message-ID: <20200720.170238.1386984311681909814.davem@davemloft.net> (raw)
In-Reply-To: <cover.1595235208.git.nicolas.ferre@microchip.com>

From: <nicolas.ferre@microchip.com>
Date: Mon, 20 Jul 2020 10:56:51 +0200

> Here is the second part of support for WoL magic-packet on the current macb
> driver. This one
> is addressing the bulk of the feature and is based on current net-next/master.
> 
> MACB and GEM code must co-exist and as they don't share exactly the same
> register layout, I had to specialize a bit the suspend/resume paths and plug a
> specific IRQ handler in order to avoid overloading the "normal" IRQ hot path.
> 
> These changes were tested on both sam9x60 which embeds a MACB+FIFO controller
> and sama5d2 which has a GEM+packet buffer type of controller.

Series applied to net-next, thanks.

      parent reply	other threads:[~2020-07-21  0:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  8:56 [PATCH v7 0/2] net: macb: Wake-on-Lan magic packet GEM and MACB handling nicolas.ferre
2020-07-20  8:56 ` [PATCH v7 1/2] net: macb: WoL support for GEM type of Ethernet controller nicolas.ferre
2020-07-20  8:56 ` [PATCH v7 2/2] net: macb: Add WoL interrupt support for MACB " nicolas.ferre
2020-07-21  0:02 ` David Miller [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=20200720.170238.1386984311681909814.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexandre.belloni@bootlin.com \
    --cc=antoine.tenart@bootlin.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=f.fainelli@gmail.com \
    --cc=harini.katakam@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.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).