arm: tegra20/colibri_t20: early pmic rail configuration
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 of 3 patches 0 repliesNew
2 of 3 patches are in this archive. The cover letter announces 3.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | arm: tegra20: implement early pmic rail configuration | +0 | 0 replies | |
| 2/3 | colibri_t20: enable early pmic rail configuration | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH 0/3] arm: tegra20/colibri_t20: early pmic rail configuration
Quoted 6 lines · Marcel Ziswiler
Quoted 3 lines · Stephen Warren
Is there any guarantee that the voltage levels are high enough for the AVP to run correctly before the CORE rail is adjusted? It sounds to me like a HW design issue; the SoC reset output should reset the PMIC too.
Quoted 7 lines
If by guarantee you mean whether it is impossible by software to completely screw the rail configuration no there is no such guarantee. But even on T30 where usually some PMIC GPIOs are used to switch to a sane default software could mess up the configuration of that as well. To prevent any of that I guess a higher level of trusted computing stuff would be required. At the end we just have to assume that regular DVFS operation should never leave it in a completely unbootable state.
That almost sounds like there's no need for this patch/series then, since we're assuming that SW won't leave the HW in a bad state. If SW can leave HW in a bad state, the only choice is to fix the issue in HW. However, perhaps you mean there are some states that are worse than others; we assume that the rails required for the AVP are always in a good state but the rails required for the CPU/CCPLEX may not be?