From: Andrew Lunn <andrew@lunn.ch>
To: Ronnie.Kunin@microchip.com
Cc: Raju.Lakkaraju@microchip.com, netdev@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, Bryan.Whitehead@microchip.com,
richardcochran@gmail.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net 3/3] net: lan743x: Address problems with wake option flags configuration sequences
Date: Tue, 12 Mar 2024 22:40:39 +0100 [thread overview]
Message-ID: <fd22d022-cad4-489c-9861-36765dd98a87@lunn.ch> (raw)
In-Reply-To: <PH8PR11MB79656DCF7806D7390C7100DE95272@PH8PR11MB7965.namprd11.prod.outlook.com>
> I understand that the TI devices give the *impression* of supporting
> both, but based on what I explained above, even if you accept
> WAKE_MAGIC and WAKE_MAGICSEGURE on a set and report them both back
> as enabled on a get; whatever behavior your hardware does will not
> be fully compliant to both specs simultaneously anyway. I discussed
> this with Raju and what we decided to do for our driver/device is
> that if you pass both WAKE_MAGIC and WAKE_MAGICSEGURE flags to us we
> will report them back as both being enabled in a subsequent get as
> you suggested, but the behavior of our driver/hardware will be as if
> you had only enabled WAKE_MAGIC.
So i agree having WAKE_MAGIC and WAKE_MAGICSECURE at the same time
seems very odd. So i see no real problem limiting the driver to only
one or the other. However, if the user does ask for both, i would say
silently ignoring one is incorrect. You should return -EOPNOTUPP to
make it clear you don't support both at the same time.
I would also say that silently ignore the Secure version is probably
the worst choice. Things should be secure by default...
Andrew
next prev parent reply other threads:[~2024-03-12 21:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 8:09 [PATCH net 0/3] net: lan743x: Fixes for multiple WOL related issues Raju Lakkaraju
2024-02-26 8:09 ` [PATCH net 1/3] net: lan743x: disable WOL upon resume to restore full data path operation Raju Lakkaraju
2024-02-26 8:27 ` Horatiu Vultur
2024-02-29 4:51 ` Raju.Lakkaraju
2024-02-27 1:38 ` Andrew Lunn
2024-02-29 4:57 ` Raju.Lakkaraju
2024-02-26 8:09 ` [PATCH net 2/3] net: lan743x: support WOL in MAC even when PHY does not Raju Lakkaraju
2024-02-26 8:28 ` Horatiu Vultur
2024-02-27 1:42 ` Andrew Lunn
2024-02-29 4:52 ` Raju.Lakkaraju
2024-02-26 8:09 ` [PATCH net 3/3] net: lan743x: Address problems with wake option flags configuration sequences Raju Lakkaraju
2024-02-27 1:58 ` Andrew Lunn
2024-02-29 8:59 ` Raju.Lakkaraju
2024-02-29 15:06 ` Andrew Lunn
2024-03-01 10:22 ` Raju.Lakkaraju
2024-03-04 11:20 ` Raju.Lakkaraju
2024-03-06 23:19 ` Andrew Lunn
2024-03-06 23:53 ` Andrew Lunn
2024-03-08 8:20 ` Raju.Lakkaraju
2024-03-08 18:56 ` Ronnie.Kunin
2024-03-12 21:40 ` Andrew Lunn [this message]
2024-03-13 0:22 ` Ronnie.Kunin
2024-03-13 0:53 ` Florian Fainelli
2024-03-13 19:52 ` Andrew Lunn
2024-03-13 20:34 ` Ronnie.Kunin
2024-03-13 20:39 ` Florian Fainelli
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=fd22d022-cad4-489c-9861-36765dd98a87@lunn.ch \
--to=andrew@lunn.ch \
--cc=Bryan.Whitehead@microchip.com \
--cc=Raju.Lakkaraju@microchip.com \
--cc=Ronnie.Kunin@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®