From: Arun Ramadoss <arun.ramadoss@microchip.com>
To: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Cc: <woojung.huh@microchip.com>, <UNGLinuxDriver@microchip.com>,
<andrew@lunn.ch>, <vivien.didelot@gmail.com>,
<f.fainelli@gmail.com>, <olteanv@gmail.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <linux@armlinux.org.uk>,
<Tristram.Ha@microchip.com>, <arun.ramadoss@microchip.com>,
<prasanna.vengateshan@microchip.com>, <hkallweit1@gmail.com>
Subject: [Patch net-next v3 0/6] net: dsa: microchip: ksz9477: enable interrupt for internal phy link detection
Date: Fri, 16 Sep 2022 14:43:42 +0530 [thread overview]
Message-ID: <20220916091348.8570-1-arun.ramadoss@microchip.com> (raw)
This patch series implements the common interrupt handling for ksz9477 based
switches and lan937x. The ksz9477 and lan937x has similar interrupt registers
except ksz9477 has 4 port based interrupts whereas lan937x has 6 interrupts.
The patch moves the phy interrupt hanler implemented in lan937x_main.c to
ksz_common.c, along with the mdio_register functionality.
v2 -> v3
- Added the common interrupt routines for girq and pirq
v1 -> v2
- Added the .port_nirqs = 2 for ksz9896
Changes in RFC -> v1
- modified the return -ENODEV to 0 if mdio node not present
Arun Ramadoss (6):
net: dsa: microchip: determine number of port irq based on switch type
net: dsa: microchip: enable phy interrupts only if interrupt enabled
in dts
net: dsa: microchip: lan937x: return zero if mdio node not present
net: dsa: microchip: move interrupt handling logic from lan937x to
ksz_common
net: dsa: microchip: use common irq routines for girq and pirq
net: phy: micrel: enable interrupt for ksz9477 phy
drivers/net/dsa/microchip/ksz_common.c | 320 +++++++++++++++++
drivers/net/dsa/microchip/ksz_common.h | 15 +-
drivers/net/dsa/microchip/lan937x_main.c | 425 -----------------------
drivers/net/phy/micrel.c | 2 +
4 files changed, 336 insertions(+), 426 deletions(-)
base-commit: da970726ea872269dc311b6dd87af8cf457b8fe9
--
2.36.1
next reply other threads:[~2022-09-16 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 9:13 Arun Ramadoss [this message]
2022-09-16 9:13 ` [Patch net-next v3 1/6] net: dsa: microchip: determine number of port irq based on switch type Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 2/6] net: dsa: microchip: enable phy interrupts only if interrupt enabled in dts Arun Ramadoss
2022-09-22 1:11 ` Jakub Kicinski
2022-09-16 9:13 ` [Patch net-next v3 3/6] net: dsa: microchip: lan937x: return zero if mdio node not present Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 4/6] net: dsa: microchip: move interrupt handling logic from lan937x to ksz_common Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 5/6] net: dsa: microchip: use common irq routines for girq and pirq Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 6/6] net: phy: micrel: enable interrupt for ksz9477 phy Arun Ramadoss
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=20220916091348.8570-1-arun.ramadoss@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=prasanna.vengateshan@microchip.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@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).