netdev - Re: [PATCH net-next v14 5/6] net: dsa: mv88e6xxx: Add support for mv88e6393x family of Marvell

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210112173724.0ed8e1ec@kernel.org>
Date:   Tue, 12 Jan 2021 17:37:24 +0100
From:   Marek Behún <kabel@...nel.org>
To:     Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc:     Vladimir Oltean <olteanv@...il.com>, netdev@...r.kernel.org,
        pavana.sharma@...i.com, vivien.didelot@...il.com,
        f.fainelli@...il.com, kuba@...nel.org, lkp@...el.com,
        davem@...emloft.net, ashkan.boldaji@...i.com, andrew@...n.ch,
        Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: Re: [PATCH net-next v14 5/6] net: dsa: mv88e6xxx: Add support for
 mv88e6393x family of Marvell

On Tue, 12 Jan 2021 16:29:09 +0000
Russell King - ARM Linux admin <linux@...linux.org.uk> wrote:

> On Tue, Jan 12, 2021 at 05:02:26PM +0100, Marek Behún wrote:
> > > > +static void mv88e6393x_phylink_validate(struct mv88e6xxx_chip *chip, int port,
> > > > +					unsigned long *mask,
> > > > +					struct phylink_link_state *state)
> > > > +{
> > > > +	if (port == 0 || port == 9 || port == 10) {
> > > > +		phylink_set(mask, 10000baseT_Full);
> > > > +		phylink_set(mask, 10000baseKR_Full);    
> > > 
> > > I think I understand the reason for declaring 10GBase-KR support in
> > > phylink_validate, in case the PHY supports that link mode on the media
> > > side, but...  
> > 
> > Hmm, yes, maybe KR shouldn't be here, but then why is it in
> > mv88e6390x_phylink_validate?  
> 
> I'm seriously thinking about changing the phylink_validate() interface
> such that the question of which link _modes_ are supported no longer
> comes up with MAC drivers, but instead MAC drivers say what interface
> modes, speeds for each interface mode, duplexes for each speed are
> supported.

Russell, I would be happy to help with such endeavour.