netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
	Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>
Subject: [PATCH v2 net-next 0/5] Interrupt support for mv88e6xxx
Date: Sun, 16 Oct 2016 19:56:48 +0200	[thread overview]
Message-ID: <1476640613-25365-1-git-send-email-andrew@lunn.ch> (raw)

This patchset add interrupt controller support to the MV88E6xxx.  This
allows access to the interrupts the internal PHY generate. These
interrupts can then be associated to a PHY device in the device tree
and used by the PHY lib, rather than polling.

Since interrupt handling needs to make MDIO bus accesses, threaded
interrupts are used. The phylib needs to request the PHY interrupt
using the threaded IRQ API. This in term allows some simplification to
the code, in that the phylib interrupt handler can directly call
phy_change(), rather than use a work queue. The work queue is however
retained for the phy_mac_interrupt() call, which can be called in hard
interrupt context.

Since RFC v1:

Keep phy_mac_interrupt() callable in hard IRQ context.

The fix to trigger the phy state machine transitions on interrupts has
already been submitted, so is dropped from here.

Added back shared interrupts support.


Andrew Lunn (5):
  net: dsa: mv88e6xxx: Implement interrupt support.
  net: phy: Use threaded IRQ, to allow IRQ from sleeping devices
  net: phy: Threaded interrupts allow some simplification
  net: phy: Use phy name when requesting the interrupt
  arm: vf610: zii devel b: Add support for switch interrupts

 .../devicetree/bindings/net/dsa/marvell.txt        |  21 +-
 arch/arm/boot/dts/vf610-zii-dev-rev-b.dts          |  51 +++++
 drivers/net/dsa/mv88e6xxx/chip.c                   | 248 ++++++++++++++++++++-
 drivers/net/dsa/mv88e6xxx/global2.c                | 139 +++++++++++-
 drivers/net/dsa/mv88e6xxx/global2.h                |  11 +
 drivers/net/dsa/mv88e6xxx/mv88e6xxx.h              |  31 +++
 drivers/net/phy/phy.c                              |  52 +++--
 drivers/net/phy/phy_device.c                       |   2 +-
 include/linux/phy.h                                |   5 +-
 9 files changed, 522 insertions(+), 38 deletions(-)

-- 
2.9.3

             reply	other threads:[~2016-10-16 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16 17:56 Andrew Lunn [this message]
2016-10-16 17:56 ` [PATCH v2 net-next 1/5] net: dsa: mv88e6xxx: Implement interrupt support Andrew Lunn
2016-10-16 17:56 ` [PATCH v2 net-next 2/5] net: phy: Use threaded IRQ, to allow IRQ from sleeping devices Andrew Lunn
2016-10-16 17:56 ` [PATCH v2 net-next 3/5] net: phy: Threaded interrupts allow some simplification Andrew Lunn
2016-10-16 17:56 ` [PATCH v2 net-next 4/5] net: phy: Use phy name when requesting the interrupt Andrew Lunn
2016-10-16 17:56 ` [PATCH v2 net-next 5/5] arm: vf610: zii devel b: Add support for switch interrupts Andrew Lunn
2016-10-17 15:18 ` [PATCH v2 net-next 0/5] Interrupt support for mv88e6xxx David Miller
2016-10-18 18:51 ` Vivien Didelot
2016-10-18 18:57   ` Andrew Lunn
2016-10-18 19:20     ` Vivien Didelot

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=1476640613-25365-1-git-send-email-andrew@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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).