[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pome4rdo.fsf@ketchup.i-did-not-set--mail-host-address--so-tickle-me>
Date: Wed, 02 Nov 2016 02:12:03 +0100
From: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...oirfairelinux.com,
"David S. Miller" <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [PATCH net-next 08/11] net: dsa: mv88e6xxx: add port duplex setter
Hi Andrew,
Andrew Lunn <andrew@...n.ch> writes:
>> int (*port_set_link)(struct mv88e6xxx_chip *chip, int port, int link);
>> +
>> + /* Port's MAC duplex mode
>> + *
>> + * Use DUPLEX_HALF or DUPLEX_FULL to force half or full duplex, or
>> + * DUPLEX_UNKNOWN for normal duplex detection.
>> + */
>> + int (*port_set_duplex)(struct mv88e6xxx_chip *chip, int port, int dup);
>
> Again, i think DUPLEX_UNFORCED, or DUPLEX_AUTO would be better.
DUPLEX_UNKNOWN and SPEED_UNKNOWN are existing values used by the
phy/ethtool interface for the phy_device. I prefered to use them when
possible instead of creating new ones.
Thanks,
Vivien
Powered by blists - more mailing lists