You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 15, 2024. It is now read-only.
@leiyu-bytedance I did not find the I2C-8 whith "i2cdetect -l" command. Let us perform these steps to narrow down this issue:
Do not revert the 0075 patch
Do not Add pca9555 into the dts file
Boot into shell, run "i2cdetect -y 8" to check if the pca9555 is persist
cd /sys/bus/i2c/devices/i2c-8
echo pca9555 SlaveAddr > new_device
@leiyu-bytedance I did not find the I2C-8 whith "i2cdetect -l" command. Let us perform these steps to narrow down this issue:
Do not revert the 0075 patch
Do not Add pca9555 into the dts file
Boot into shell, run "i2cdetect -y 8" to check if the pca9555 is persist
cd /sys/bus/i2c/devices/i2c-8
echo pca9555 SlaveAddr > new_device
Check if you can load the driver manually
Yup, if I do not add the device in dts and load the driver after BMC is booted, it's OK.
The issue only occurs when the device is in dts.
Please be noted that the device has to be in dts, because it exposes the GPIOs for other devices (e.g. gpio-keys-polled)
If we add pca9555 in dts, it fails to probe with below errors:
The example dts is:
If we revert the patch https://github.com/Intel-BMC/openbmc/blob/intel/meta-openbmc-mods/meta-common/recipes-kernel/linux/linux-aspeed/0075-Refine-initialization-flow-in-I2C-driver.patch, the issue is gone.
So it looks like something is wrong with the patch.
The text was updated successfully, but these errors were encountered: