On 12/06/26 11:03, Jai Luthra wrote:
Hi Siddharth,
Quoting Siddharth Vadapalli (2026-06-12 10:03:31)
[TRIMMED]
I hope this clarifies your question. Let me know otherwise.
Thanks, that makes a lot of sense.
Given the failure happens once in two weeks with hundred of tests, I have a
slight preference for keeping the default to not call phy_config()
everytime, or maybe just documenting this environment variable prominently
somewhere, as most developers with a board on their desk would prefer a
broken link every two weeks as opposed to slow transfers.
But I understand anywhere with automation it's okay to spend a little more
time and keep it robust.
I agree that users may not be aware of this feature unless it is
documented. Since the environment variable is TI specific, I assume that it
cannot be documented in the common environment variable documentation at:
https://docs.u-boot-project.org/en/latest/usage/environment.html
Instead, it probably needs to be documented in both:
https://docs.u-boot-project.org/en/latest/board/ti/k3.html (TI K3 boards)
https://docs.u-boot-project.org/en/latest/board/beagle/index.html#arm-based-boards
(Beagleboard documentation for K3 SoCs)
Let me know if you have any suggestions regarding a better place to
document it. Thank you for reviewing the patch and providing your feedback.
Regards,
Siddharth.
