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  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]
Date:   Sun, 17 May 2020 19:58:20 +0200
From:   Andrew Lunn <>
To:     Baruch Siach <>
Cc:     Russell King - ARM Linux admin <>,
        Florian Fainelli <>,
        Heiner Kallweit <>,
Subject: Re: [RFC PATCH] drivers: net: mdio_bus: try indirect clause 45 regs

> > I don't think this should be done at mdiobus level; I think this is a
> > layering violation.  It needs to happen at the PHY level because the
> > indirect C45 access via C22 registers is specific to PHYs.
> >
> > It also needs to check in the general case that the PHY does indeed
> > support the C22 register set - not all C45 PHYs do.
> >
> > So, I think we want this fallback to be conditional on:
> >
> > - are we probing for the PHY, trying to read its IDs and
> >   devices-in-package registers - if yes, allow fallback.
> > - does the C45 PHY support the C22 register set - if yes, allow
> >   fallback.
> I'll take a look. Thanks.
Hi Baruch

Another option to consider is a third compatible string. We have
compatibles for C22, C45. Add another one for C45 over C22, and have
the core support it as the third access method next to C22 and C45.

We already rely on the DT author getting C22 vs C45 correct for the
hardware. Is it too much to ask they get it write when there are three

As to your particular hardware, if i remember correctly, some of the
Marvell SoCs have mdio and xmdio bus masters. The mdio bus can only do
C22, and the xmdio can only do C45. Have the hardware engineers put
the PHY on the wrong bus?


Powered by blists - more mailing lists