From: Andrew Lunn <andrew@lunn.ch>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
linux@armlinux.org.uk, pavana.sharma@digi.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH v5 3/4] net: dsa: mv88e6xxx: Add serdes interrupt support for MV88E6097
Date: Wed, 25 Nov 2020 02:20:48 +0100 [thread overview]
Message-ID: <20201125012048.GD2075216@lunn.ch> (raw)
In-Reply-To: <20201124043440.28400-4-chris.packham@alliedtelesis.co.nz>
On Tue, Nov 24, 2020 at 05:34:39PM +1300, Chris Packham wrote:
> The MV88E6097 presents the serdes interrupts for ports 8 and 9 via the
> Switch Global 2 registers. There is no additional layer of
> enablinh/disabling the serdes interrupts like other mv88e6xxx switches.
enabling
> Even though most of the serdes behaviour is the same as the MV88E6185
> that chip does not provide interrupts for serdes events so unlike
> earlier commits the functions added here are specific to the MV88E6097.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2020-11-25 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 4:34 [net-next PATCH v5 0/4] net: dsa: mv88e6xxx: serdes link without phy Chris Packham
2020-11-24 4:34 ` [net-next PATCH v5 1/4] net: dsa: mv88e6xxx: Don't force link when using in-band-status Chris Packham
2020-11-25 0:33 ` Andrew Lunn
2020-11-24 4:34 ` [net-next PATCH v5 2/4] net: dsa: mv88e6xxx: Support serdes ports on MV88E6097/6095/6185 Chris Packham
2020-11-24 4:34 ` [net-next PATCH v5 3/4] net: dsa: mv88e6xxx: Add serdes interrupt support for MV88E6097 Chris Packham
2020-11-25 1:20 ` Andrew Lunn [this message]
2020-11-24 4:34 ` [net-next PATCH v5 4/4] net: dsa: mv88e6xxx: Handle error in serdes_get_regs Chris Packham
2020-11-26 2:10 ` [net-next PATCH v5 0/4] net: dsa: mv88e6xxx: serdes link without phy patchwork-bot+netdevbpf
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=20201125012048.GD2075216@lunn.ch \
--to=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=f.fainelli@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=pavana.sharma@digi.com \
--cc=vivien.didelot@gmail.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).