Thread (21 messages) flat view 21 messages, 2 authors, 2016-11-02

Re: [PATCH net-next 07/11] net: dsa: mv88e6xxx: add port link setter

From: Andrew Lunn <andrew@lunn.ch>
Date: 2016-11-02 09:16:35
Also in: lkml

On Wed, Nov 02, 2016 at 02:07:09AM +0100, Vivien Didelot wrote:
Hi Andrew,

Andrew Lunn [off-list ref] writes:
quoted
quoted
+#define LINK_UNKNOWN	-1
+
+	/* Port's MAC link state
+	 * LINK_UNKNOWN for normal link detection, 0 to force link down,
+	 * otherwise force link up.
+	 */
+	int (*port_set_link)(struct mv88e6xxx_chip *chip, int port, int link);
Maybe LINK_AUTO would be better than UNKNOWN? Or LINK_UNFORCED.
I used LINK_UNKNOWN to be consistent with the supported SPEED_UNKNOWN
and DUPLEX_UNKNOWN values of PHY devices.
Hi Vivien

These are i think for reporting back to user space what duplex or link
is currently being used. But here you are setting, not
reporting. Setting something to an unknown state is rather odd, and in
fact, it is not unknown, it is unforced.

      Andrew
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help