HWMon interface for I2C thermal device (TMP102, 3.10) - missing sysfs files
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am trying to get the TMP102 kernel module functioning on an x86_64 machine running CentOS 7.6 (kernel 3.10). The system has 3 TMP102 sensors attached to an I2C bus (Designware I2C adapter).
When I load the TMP102 sensor module (source tree here), the module appears to detect all three of the sensors. At the tail of dmesg I see the "initiated" statements that display the I2C address for each sensor(from line 207 of source).
"Root" hwmon# sysfs files are creates for each sensor (e.g., /sys/class/hwmon/hwmon#), but inside of each of these nodes the attribute files (input, max, and max_hyst) are missing; so no data can be queried from any of the sensors through sysfs.
I'm not sure exactly what is going wrong here. I've compared the driver code with similar sensors and they appear to follow the same overall pattern (registering attributes to the parent device node).
When I run i2c-detect, the sensors are visible. I can also query the sensors directly over the I2C bus and retrieve the current value without a problem; but I would prefer to use the TMP102 driver and sysfs for consistency.
Does anyone have any idea why the sysfs files are failing to be created, and/or the next steps I can take to fix and/or debug the issue?
kernel-modules hardware temperature sensors
edited Aug 8 at 3:50
slm♦
238k65491662
asked Aug 7 at 19:59
Jeffrey P
161
add a comment |Â
up vote
1
down vote
favorite
I am trying to get the TMP102 kernel module functioning on an x86_64 machine running CentOS 7.6 (kernel 3.10). The system has 3 TMP102 sensors attached to an I2C bus (Designware I2C adapter).
When I load the TMP102 sensor module (source tree here), the module appears to detect all three of the sensors. At the tail of dmesg I see the "initiated" statements that display the I2C address for each sensor(from line 207 of source).
"Root" hwmon# sysfs files are creates for each sensor (e.g., /sys/class/hwmon/hwmon#), but inside of each of these nodes the attribute files (input, max, and max_hyst) are missing; so no data can be queried from any of the sensors through sysfs.
I'm not sure exactly what is going wrong here. I've compared the driver code with similar sensors and they appear to follow the same overall pattern (registering attributes to the parent device node).
When I run i2c-detect, the sensors are visible. I can also query the sensors directly over the I2C bus and retrieve the current value without a problem; but I would prefer to use the TMP102 driver and sysfs for consistency.
Does anyone have any idea why the sysfs files are failing to be created, and/or the next steps I can take to fix and/or debug the issue?
kernel-modules hardware temperature sensors
edited Aug 8 at 3:50
slm♦
238k65491662
asked Aug 7 at 19:59
Jeffrey P
161
Sounds like your issue - stackoverflow.com/questions/37507609/….
– slm♦
Aug 8 at 3:52
Docs on this H/W - ti.com/tool/tmp102sw-linux.
– slm♦
Aug 8 at 3:56
Looking at this - github.com/Mellanox/mlxsw/wiki/Temperature-and-Fan-Control I suspect your H/W is not getting fully detected by the tmp102 driver.
– slm♦
Aug 8 at 4:04
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to get the TMP102 kernel module functioning on an x86_64 machine running CentOS 7.6 (kernel 3.10). The system has 3 TMP102 sensors attached to an I2C bus (Designware I2C adapter).
When I load the TMP102 sensor module (source tree here), the module appears to detect all three of the sensors. At the tail of dmesg I see the "initiated" statements that display the I2C address for each sensor(from line 207 of source).
"Root" hwmon# sysfs files are creates for each sensor (e.g., /sys/class/hwmon/hwmon#), but inside of each of these nodes the attribute files (input, max, and max_hyst) are missing; so no data can be queried from any of the sensors through sysfs.
I'm not sure exactly what is going wrong here. I've compared the driver code with similar sensors and they appear to follow the same overall pattern (registering attributes to the parent device node).
When I run i2c-detect, the sensors are visible. I can also query the sensors directly over the I2C bus and retrieve the current value without a problem; but I would prefer to use the TMP102 driver and sysfs for consistency.
Does anyone have any idea why the sysfs files are failing to be created, and/or the next steps I can take to fix and/or debug the issue?
kernel-modules hardware temperature sensors
edited Aug 8 at 3:50
slm♦
238k65491662
asked Aug 7 at 19:59
Jeffrey P
161
I am trying to get the TMP102 kernel module functioning on an x86_64 machine running CentOS 7.6 (kernel 3.10). The system has 3 TMP102 sensors attached to an I2C bus (Designware I2C adapter).
When I load the TMP102 sensor module (source tree here), the module appears to detect all three of the sensors. At the tail of dmesg I see the "initiated" statements that display the I2C address for each sensor(from line 207 of source).
"Root" hwmon# sysfs files are creates for each sensor (e.g., /sys/class/hwmon/hwmon#), but inside of each of these nodes the attribute files (input, max, and max_hyst) are missing; so no data can be queried from any of the sensors through sysfs.
I'm not sure exactly what is going wrong here. I've compared the driver code with similar sensors and they appear to follow the same overall pattern (registering attributes to the parent device node).
When I run i2c-detect, the sensors are visible. I can also query the sensors directly over the I2C bus and retrieve the current value without a problem; but I would prefer to use the TMP102 driver and sysfs for consistency.
Does anyone have any idea why the sysfs files are failing to be created, and/or the next steps I can take to fix and/or debug the issue?
kernel-modules hardware temperature sensors
kernel-modules hardware temperature sensors
edited Aug 8 at 3:50
slm♦
238k65491662
asked Aug 7 at 19:59
Jeffrey P
161
edited Aug 8 at 3:50
slm♦
238k65491662
asked Aug 7 at 19:59
Jeffrey P
161
edited Aug 8 at 3:50
slm♦
238k65491662
edited Aug 8 at 3:50
slm♦
238k65491662
edited Aug 8 at 3:50
slm♦
238k65491662
238k65491662
asked Aug 7 at 19:59
Jeffrey P
161
asked Aug 7 at 19:59
Jeffrey P
161
asked Aug 7 at 19:59
Jeffrey P
161
161
Sounds like your issue - stackoverflow.com/questions/37507609/….
– slm♦
Aug 8 at 3:52
Docs on this H/W - ti.com/tool/tmp102sw-linux.
– slm♦
Aug 8 at 3:56
Looking at this - github.com/Mellanox/mlxsw/wiki/Temperature-and-Fan-Control I suspect your H/W is not getting fully detected by the tmp102 driver.
– slm♦
Aug 8 at 4:04
add a comment |Â
Sounds like your issue - stackoverflow.com/questions/37507609/….
– slm♦
Aug 8 at 3:52
Docs on this H/W - ti.com/tool/tmp102sw-linux.
– slm♦
Aug 8 at 3:56
Looking at this - github.com/Mellanox/mlxsw/wiki/Temperature-and-Fan-Control I suspect your H/W is not getting fully detected by the tmp102 driver.
– slm♦
Aug 8 at 4:04
Sounds like your issue - stackoverflow.com/questions/37507609/….
– slm♦
Aug 8 at 3:52
Sounds like your issue - stackoverflow.com/questions/37507609/….
– slm♦
Aug 8 at 3:52
Docs on this H/W - ti.com/tool/tmp102sw-linux.
– slm♦
Aug 8 at 3:56
Docs on this H/W - ti.com/tool/tmp102sw-linux.
– slm♦
Aug 8 at 3:56
Looking at this - github.com/Mellanox/mlxsw/wiki/Temperature-and-Fan-Control I suspect your H/W is not getting fully detected by the tmp102 driver.
– slm♦
Aug 8 at 4:04
Looking at this - github.com/Mellanox/mlxsw/wiki/Temperature-and-Fan-Control I suspect your H/W is not getting fully detected by the tmp102 driver.
– slm♦
Aug 8 at 4:04
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f461160%2fhwmon-interface-for-i2c-thermal-device-tmp102-3-10-missing-sysfs-files%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sounds like your issue - stackoverflow.com/questions/37507609/….
– slm♦
Aug 8 at 3:52
Docs on this H/W - ti.com/tool/tmp102sw-linux.
– slm♦
Aug 8 at 3:56
Looking at this - github.com/Mellanox/mlxsw/wiki/Temperature-and-Fan-Control I suspect your H/W is not getting fully detected by the tmp102 driver.
– slm♦
Aug 8 at 4:04