From: Hans de Goede on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3431#note_2146020083 Correction / self nack. Even though the designware I2C controllers in e.g. Raptor Lake are PCI devices they do not use the i2c-desigware-pcidrv module. Instead they use the intel-lpss PCI driver which creates a platform_device child which then uses the i2c-desigware-platdrv. This explains why the lack of CONFIG_I2C_DESIGNWARE_PCI=m was not an issue on RHEL10 before. Fedora needs CONFIG_I2C_DESIGNWARE_PCI for some older hw. It seems that all x86_64-v3 hw uses the intel-lpss PCI driver which then instantiates a platform-device, which was confusing me. I'll push an updated, fixed version dropping the CONFIG_I2C_DESIGNWARE_PCI change. Note CONFIG_I2C_DESIGNWARE_PCI is necessary for Intel Elkhartlake Atom x6000E IOT processors. It is unclear to me if those can handle x86_64-v3, if they can we may need to revisit enabling CONFIG_I2C_DESIGNWARE_PCI=m on x86. And CONFIG_I2C_DESIGNWARE_PCI is also necessary for the I2C controller used to talk to the Type-C controller for the Type-C port found on some NAVI cards. Regardless, lets drop this part of the change and then maybe revisit with a better commit message explaining why this is necessary. -- _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
