Orin的hwmon路径会变化

您好,我在使用pwm1时发现orin路径在重启后会发生变化,比如第一次开机pwm1在/sys/class/hwmon2中,重启orin后pwm1会在/sys/class/hwmon4中,再重启又会回到/sys/class/hwmon2中,一直循环这个过程,这是为什么,能否让他固定。

Hi,
Do you observe the issue on AGX Orin developer kit? We try this on Jetpack 5.1.2 Orin developer kit and the paths are not changed:

root@tegra-ubuntu:/home/nvidia# cat /sys/class/hwmon/hwmon0/name
pwm_tach
root@tegra-ubuntu:/home/nvidia# cat /sys/class/hwmon/hwmon1/name
soctherm_oc
root@tegra-ubuntu:/home/nvidia# cat /sys/class/hwmon/hwmon2/name
pwmfan
root@tegra-ubuntu:/home/nvidia# cat /sys/class/hwmon/hwmon3/name
ina3221
root@tegra-ubuntu:/home/nvidia# cat /sys/class/hwmon/hwmon4/name
ina3221
root@tegra-ubuntu:/home/nvidia# cat /sys/class/hwmon/hwmon5/name
ucsi_source_psy_1_00081
root@tegra-ubuntu:/home/nvidia# cat /sys/class/hwmon/hwmon6/name
ucsi_source_psy_1_00082
root@tegra-ubuntu:/home/nvidia# cat /sys/class/hwmon/hwmon7/name
6810000ethernet00

是的,在agx orin上有这个问题,但我使用的是5.1.1工具包

现在我需要用到的pwm1是在hwmon4中,再开机就会到hwmon2中

test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon0
device  name  of_node  power  rpm  subsystem  uevent
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon1
device  name  oc1_event_cnt  oc1_throt_en  oc2_event_cnt  oc2_throt_en  oc3_event_cnt  oc3_throt_en  of_node  power  subsystem  uevent
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon2
curr1_crit        curr2_crit        curr3_crit        curr4_crit        in1_input   in3_enable  in6_input  power            subsystem
curr1_crit_alarm  curr2_crit_alarm  curr3_crit_alarm  curr4_crit_alarm  in1_label   in3_input   in7_input  samples          uevent
curr1_input       curr2_input       curr3_input       curr4_input       in2_enable  in3_label   in7_label  shunt1_resistor  update_interval
curr1_max         curr2_max         curr3_max         device            in2_input   in4_input   name       shunt2_resistor
curr1_max_alarm   curr2_max_alarm   curr3_max_alarm   in1_enable        in2_label   in5_input   of_node    shunt3_resistor
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon3
curr1_crit        curr2_crit        curr3_crit        curr4_crit        in1_input   in3_enable  in6_input  power            subsystem
curr1_crit_alarm  curr2_crit_alarm  curr3_crit_alarm  curr4_crit_alarm  in1_label   in3_input   in7_input  samples          uevent
curr1_input       curr2_input       curr3_input       curr4_input       in2_enable  in3_label   in7_label  shunt1_resistor  update_interval
curr1_max         curr2_max         curr3_max         device            in2_input   in4_input   name       shunt2_resistor
curr1_max_alarm   curr2_max_alarm   curr3_max_alarm   in1_enable        in2_label   in5_input   of_node    shunt3_resistor
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon4
device  name  of_node  power  pwm1  subsystem  uevent
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon5
device  name  power  subsystem  temp1_input  uevent
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon6
device  of_node  subsystem   temp1_crit_alarm  temp1_lcrit        temp1_max        temp1_min        uevent
name    power    temp1_crit  temp1_input       temp1_lcrit_alarm  temp1_max_alarm  temp1_min_alarm
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon7
device  of_node  subsystem   temp1_crit_alarm  temp1_lcrit        temp1_max        temp1_min        uevent
name    power    temp1_crit  temp1_input       temp1_lcrit_alarm  temp1_max_alarm  temp1_min_alarm
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon8
device  of_node  subsystem   temp1_crit_alarm  temp1_lcrit        temp1_max        temp1_min        uevent
name    power    temp1_crit  temp1_input       temp1_lcrit_alarm  temp1_max_alarm  temp1_min_alarm
test@tegra-ubuntu:/sys/class/hwmon$ ls hwmon9
device  of_node  subsystem   temp1_crit_alarm  temp1_lcrit        temp1_max        temp1_min        uevent
name    power    temp1_crit  temp1_input       temp1_lcrit_alarm  temp1_max_alarm  temp1_min_alarm

Blockquote

Hi,
We have discussion with our team and it looks not possible to fix the index. Suggest you check the name to make sure you are reading the data from which monitor.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.