Aspeed2600 EVB Hwmon problem
Eric.Wetterlind at gd-ms.com
Eric.Wetterlind at gd-ms.com
Fri May 14 07:42:58 AEST 2021
Hello,
I am currently trying to add a simple temp sensor to my image, which is based off of the evb-ast2600 image. I have successfully been able to add this sensor to a ast2500-based image, but the 2600 is not cooperating. Any pointers would be greatly appreciated (and sanity-saving), as I am near the end of all paths I know of.
Project bblayers.conf.sample contains the following:
==========
##OEROOT##/meta \
##OEROOT##/meta-poky \
##OEROOT##/meta-openembedded/meta-oe \
##OEROOT##/meta-openembedded/meta-networking \
##OEROOT##/meta-openembedded/meta-python \
##OEROOT##/meta-phosphor \
##OEROOT##/meta-aspeed \
##OEROOT##/meta-ourproject \
===========
The device tree has this (and using the standard aspeed_g6_dtsi):
===========
&i2c1 {
status = "okay";
tmp423 at 4c {
compatible = "ti,tmp423";
reg = <0x4c>;
};
};
===========
Recipes-phosphor/sensors contains the directory structure phosphor-hwmon/obmc/hwmon/ahb/apb/bus at 1e78a000/i2c-bus at 100, with tmp423.conf in it.
The phosphor-hwmon_%.bbappend file contains this:
===========
FILESEXTRAPATHS_prepend_ourproject := "${THISDIR}/${PN}:"
EXTRA_OECONF_append_ourproject = " --enable-negative-errno-on-fail"
CHIPS = " \
bus at 1e78a000/i2c-bus at 100/tmp423 at 4c \
"
ITEMSFMT = "ahb/apb/{0}.conf"
ITEMS = "${@compose_list(d, 'ITEMSFMT', 'CHIPS')}"
ENVS = "obmc/hwmon/{0}"
SYSTEMD_ENVIRONMENT_FILE_${PN}_append_ourproject = " ${@compose_list(d, 'ENVS', 'ITEMS')}"
===========
When booting up in Qemu, the device is recognized:
===========
#cat /sys/firmware/devicetree/base/ahb/apb/bus at 1e78a000/i2c-bus at 100/tmp423 at 4c/compatible
ti,tmp423
# cat /sys/devices/platform/ahb/ahb\:apb/ahb\:apb\:bus\@1e78a000/1e78a100.i2c-bus/i2c-1/1-004c/name
tmp423
===========
There is even a link in /sys/bus/i2c/devices/1-004c to /sys/devices/platform/ahb/ahb\:apb/ahb\:apb\:bus\@1e78a000/1e78a100.i2c-bus/i2c-1/1-004c.
The .conf file shows up in /etc/default/obmc/hwmon/ahb/apb/bus at 1e78a000/i2c-bus at 100.
The problem is that nothing ever gets populated into /sys/class/hwmon. It is an empty directory. On our ast2400 and ast2500 images, this same procedure, stripped down to almost the exact same specs as I've mentioned above, produces a link as /sys/class/hwmon/hwmon0.
What am I missing?
Regards,
-Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20210513/85733fce/attachment.htm>
More information about the openbmc
mailing list