On 21 May 2014 23:33, Akshay Saraswat akshay.s@samsung.com wrote:
From: Doug Anderson dianders@chromium.org
From experiments it appears that PHY_CON13 is glitchy if we sample it when CLKM is running. If we stop CLKM when sampling it the glitches all go away, so we'll do that.
We also check the "is it locked" bits of PHY_CON13 and loop until they show that the value sampled actually represents a locked value. It doesn't appear that the glitching and "is it locked" are related, but it seems wise to wait until the PHY tells us the value is good before we use it. In practice we will not loop more than a couple times (and usually won't loop at all).
Signed-off-by: Doug Anderson dianders@chromium.org Signed-off-by: Akshay Saraswat akshay.s@samsung.com
Acked-by: Simon Glass sjg@chromium.org