Which part of carrier board power section is related to this over-current soctherm oc issue?
How does cri_current_limit_0 detect over current event ?
Which kernel driver attribute value can be checked?
If i don’t build soctherm in dts . Will it have any risk for running 4.6 on TX2NX without this detection?
I’ve modified criti_current_limit_0 to 5000ma
but it still show throttle over-current warning on our carrier board.
It doesn’t show warning on devkit.
I’ve tested NX and TX2NX on both devkit and our carrier board, and taken some screenshot of driver’s attributes.
Which value does soctherm oc threshold 5000mA/3600mA monitor for?
Is it in_current0_input or other?
Does the value mean for VDD_IN 5V 's cureent mA?
And sometimes i found ina3221x will unavailable on i2c .
When i tried to cat values , it will stuck for awhile and shows “Connection timeout” ,it also shows throttle over-current event at this condition .
soctherm it’s used to monitor temperature.
since you’re able to run the use-case on the DevKits, please review your board design.
in addition, please access Carrier Board Specification, and check [Table 5-2. Interface Supply Current Capabilities] to check the max current for reference,
this current-critical-limit-ma modification only for test purpose,
we don’t suggest to increase OC limit higher than default value for your all finalize products.