Skip to contentSkip to conversation

arm: tegra20: implement early pmic rail configuration

PATCH New Marcel Ziswiler 2 participants 2 messages Aug 20, 2015 – Aug 24, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/3 arm: tegra20: implement early pmic rail configuration

Quoted 2 lines · Stephen Warren

Does the CORE rail get adjusted by DVFS? Hopefully if it does, it is never set so low that AVP operation at reset is impossible...

Exactly.

Quoted 4 lines
Quoted 1 line

+ udelay(1000);

all the delays in this patch seem very large. What drove the choice of the delay values?

Three things: I2C transfers at that speed will take at least around some 3 to 4 hundred us to complete so we stay at the save side. Plus the T30 equivalent file uses the exact same delays so it can't be that wrong. My testing also showed that setting it anywhere much lower will cause reliability issues.

#1 lore raw

PATCH 1/3 arm: tegra20: implement early pmic rail configuration

Quoted 7 lines · Marcel Ziswiler
Quoted 2 lines · Stephen Warren

Does the CORE rail get adjusted by DVFS? Hopefully if it does, it is never set so low that AVP operation at reset is impossible...

Exactly.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

+ udelay(1000);

all the delays in this patch seem very large. What drove the choice of the delay values?

Three things: I2C transfers at that speed will take at least around some 3 to 4 hundred us to complete so we stay at the save side.

The I2C transfers should have already synchronously completed, so there should be no need to wait for those. If that's not true, there's a serious bug that needs to be fixed.

Quoted 4 lines

Plus the T30
equivalent file uses the exact same delays so it can't be that wrong. My testing also showed that setting it anywhere much lower will cause reliability issues.

OK, consistency with other code seems reasonable. I still think there's little point in such long delays though, but that could be fixed later.