[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yd7UHYeAl3wigMmr@lunn.ch>
Date: Wed, 12 Jan 2022 14:14:05 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Martin Schiller <ms@....tdt.de>
Cc: Tim Harvey <tharvey@...eworks.com>,
Hauke Mehrtens <hauke@...ke-m.de>,
martin.blumenstingl@...glemail.com,
Florian Fainelli <f.fainelli@...il.com>, hkallweit1@...il.com,
Russell King - ARM Linux <linux@...linux.org.uk>,
David Miller <davem@...emloft.net>, kuba@...nel.org,
netdev <netdev@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v6] net: phy: intel-xway: Add RGMII internal
delay configuration
> > If I add a 'genphy_soft_reset(phydev);' at the top of
> > xway_gphy_rgmii_init before the write to XWAY_MDIO_MIICTRL the values
> > do take effect so perhaps that's the proper fix.
>
> OK, I see that we have to change something here.
> But I would like to avoid a complete reset (BMCR_RESET) if possible.
What does the datasheet say about BMCR_RESET? Some PHYs, like Marvell,
it only resets the internal state machines. Register values are not
changed back to defaults or anything like that. Also for many register
writes in Marvell PHYs the write does not take effect until the next
reset.
So a BMCR_RESET can be the correct thing to do.
Andrew
Powered by blists - more mailing lists