On Sun, May 17, 2020 at 10:51:50PM +0200, Andrew Lunn wrote:
> > > +static int marvell_vct5_amplitude_distance(struct phy_device *phydev,
> > > + int meters)
> > > +{
> > > + int mV_pair0, mV_pair1, mV_pair2, mV_pair3;
> > > + int distance;
> > >
On Sun, May 17, 2020 at 1:51 PM Andrew Lunn wrote:
>
> > > +static int marvell_vct5_amplitude_distance(struct phy_device *phydev,
> > > + int meters)
> > > +{
> > > + int mV_pair0, mV_pair1, mV_pair2, mV_pair3;
> > > + int distance;
> > > +
> > +static int marvell_vct5_amplitude_distance(struct phy_device *phydev,
> > + int meters)
> > +{
> > + int mV_pair0, mV_pair1, mV_pair2, mV_pair3;
> > + int distance;
> > + u16 reg;
> > + int err;
> > +
> > + distance = meter
On Sun, May 17, 2020 at 12:59 PM Andrew Lunn wrote:
>
> The Marvell PHYs can measure the amplitude of the returned signal for
> a given distance. Implement this option of the cable test
> infrastructure.
>
> Signed-off-by: Andrew Lunn
> ---
> drivers/net/phy/marvell.c | 227 +
The Marvell PHYs can measure the amplitude of the returned signal for
a given distance. Implement this option of the cable test
infrastructure.
Signed-off-by: Andrew Lunn
---
drivers/net/phy/marvell.c | 227 +-
1 file changed, 226 insertions(+), 1 deletion(-)
