From: Andrew Lunn <andrew@lunn.ch>
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, bryan.whitehead@microchip.com,
lxu@maxlinear.com, richardcochran@gmail.com,
UNGLinuxDriver@microchip.com, Ian.Saturley@microchip.com
Subject: Re: [PATCH net-next 2/5] net: lan743x: Add support to Secure-ON WOL
Date: Tue, 14 Jun 2022 22:59:21 +0200 [thread overview]
Message-ID: <Yqj2qegsJ7UTEr0K@lunn.ch> (raw)
In-Reply-To: <20220614103424.58971-3-Raju.Lakkaraju@microchip.com>
On Tue, Jun 14, 2022 at 04:04:21PM +0530, Raju Lakkaraju wrote:
> Add support to Magic Packet Detection with Secure-ON for PCI11010/PCI11414 chips
>
> Signed-off-by: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
> ---
> .../net/ethernet/microchip/lan743x_ethtool.c | 14 +++++++++
> drivers/net/ethernet/microchip/lan743x_main.c | 29 +++++++++++++++++++
> drivers/net/ethernet/microchip/lan743x_main.h | 10 +++++++
> 3 files changed, 53 insertions(+)
>
> diff --git a/drivers/net/ethernet/microchip/lan743x_ethtool.c b/drivers/net/ethernet/microchip/lan743x_ethtool.c
> index 48b19dcd4351..b591a7aea937 100644
> --- a/drivers/net/ethernet/microchip/lan743x_ethtool.c
> +++ b/drivers/net/ethernet/microchip/lan743x_ethtool.c
> @@ -1149,7 +1149,13 @@ static void lan743x_ethtool_get_wol(struct net_device *netdev,
> wol->supported |= WAKE_BCAST | WAKE_UCAST | WAKE_MCAST |
> WAKE_MAGIC | WAKE_PHY | WAKE_ARP;
>
> + if (adapter->is_pci11x1x)
> + wol->supported |= WAKE_MAGICSECURE;
> +
> wol->wolopts |= adapter->wolopts;
> + if (adapter->wolopts & WAKE_MAGICSECURE)
> + memcpy(wol->sopass, adapter->sopass,
> + SOPASS_MAX * sizeof(wol->sopass[0]));
sizeof(wol->sopass) is simpler. That is what other drivers use.
> + if (wol->wolopts & WAKE_MAGICSECURE &&
> + wol->wolopts & WAKE_MAGIC) {
> + memcpy(adapter->sopass, wol->sopass,
> + SOPASS_MAX * sizeof(wol->sopass[0]));
> + adapter->wolopts |= WAKE_MAGICSECURE;
> + } else {
> + memset(adapter->sopass, 0, sizeof(u8) * SOPASS_MAX);
> + }
Same here.
Andrew
next prev parent reply other threads:[~2022-06-14 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 10:34 [PATCH net-next 0/5] net: lan743x: PCI11010 / PCI11414 devices Enhancements Raju Lakkaraju
2022-06-14 10:34 ` [PATCH net-next 1/5] net: lan743x: Add support to LAN743x register dump Raju Lakkaraju
2022-06-14 10:34 ` [PATCH net-next 2/5] net: lan743x: Add support to Secure-ON WOL Raju Lakkaraju
2022-06-14 20:59 ` Andrew Lunn [this message]
2022-06-15 9:44 ` Raju Lakkaraju
2022-06-14 10:34 ` [PATCH net-next 3/5] net: lan743x: Add support to SGMII block access functions Raju Lakkaraju
2022-06-14 21:03 ` Andrew Lunn
2022-06-15 9:36 ` Raju Lakkaraju
2022-06-14 10:34 ` [PATCH net-next 4/5] net: lan743x: Add support to SGMII 1G and 2.5G Raju Lakkaraju
2022-06-14 21:13 ` Andrew Lunn
2022-06-15 9:39 ` Raju Lakkaraju
2022-06-14 10:34 ` [PATCH net-next 5/5] net: phy: add support to get Master-Slave configuration Raju Lakkaraju
2022-06-14 21:21 ` Andrew Lunn
2022-06-15 9:43 ` Raju Lakkaraju
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=Yqj2qegsJ7UTEr0K@lunn.ch \
--to=andrew@lunn.ch \
--cc=Ian.Saturley@microchip.com \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lxu@maxlinear.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@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).