From: John Crispin <john@phrozen.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Felix Fietkau <nbd@nbd.name>, Sean Wang <keyhaede@gmail.com>,
netdev@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org, John Crispin <john@phrozen.org>
Subject: [PATCH 0/4] net-next: mediatek: IRQ cleanups, fixes and grouping
Date: Wed, 15 Jun 2016 16:58:46 +0200 [thread overview]
Message-ID: <1466002730-58476-1-git-send-email-john@phrozen.org> (raw)
This series contains 2 small code cleanups that are leftovers from the
MIPS support. There is also a small fix that adds proper locking to the
code accessing the IRQ registers. Without this fix we saw deadlocks caused
by the last patch of the series, which adds IRQ grouping. The grouping
feature allows us to use different IRQs for TX and RX. By doing so we can
use affinity to let the SoC handle the IRQs on different cores.
John Crispin (4):
net-next: mediatek: remove superfluous register reads
net-next: mediatek: don't use intermediate variables to store IRQ
masks
net-next: mediatek: add IRQ locking
net-next: mediatek: add support for IRQ grouping
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 175 +++++++++++++++++----------
drivers/net/ethernet/mediatek/mtk_eth_soc.h | 16 ++-
2 files changed, 122 insertions(+), 69 deletions(-)
--
1.7.10.4
next reply other threads:[~2016-06-15 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 14:58 John Crispin [this message]
2016-06-15 14:58 ` [PATCH 1/4] net-next: mediatek: remove superfluous register reads John Crispin
2016-06-15 14:58 ` [PATCH 2/4] net-next: mediatek: don't use intermediate variables to store IRQ masks John Crispin
2016-06-15 14:58 ` [PATCH 3/4] net-next: mediatek: add IRQ locking John Crispin
2016-06-15 14:58 ` [PATCH 4/4] net-next: mediatek: add support for IRQ grouping John Crispin
2016-06-16 5:20 ` [PATCH 0/4] net-next: mediatek: IRQ cleanups, fixes and grouping David Miller
2016-06-16 9:44 ` John Crispin
2016-06-16 9:51 ` Daniel Borkmann
2016-06-17 0:27 ` David Miller
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=1466002730-58476-1-git-send-email-john@phrozen.org \
--to=john@phrozen.org \
--cc=davem@davemloft.net \
--cc=keyhaede@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
/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).