On Wed, May 18, 2022 at 06:49:59PM +0000, Limonciello, Mario wrote: > [Public] > > Hi, > > Some users have complained that i2c the controller doesn't work on newer designs. This is because the system can be configured by an OEM to not allow access to the I2C controller registers via legacy methods and instead requires MMIO. > > Some bug reports collecting this problem (which have had duplicates brought in) > https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984 > https://bugs.launchpad.net/amd/+bug/1950062 > > These commits that have landed into 5.18 fix this issue both for i2c-piix4 and for sp5100-tco (which suffers the same fate). > > Would you take them back to stable 5.15.y and 5.17.y? The series comes back cleanly to both. > > 27c196c7b73c kernel/resource: Introduce request_mem_region_muxed() > 93102cb44978 i2c: piix4: Replace hardcoded memory map size with a #define > a3325d225b00 i2c: piix4: Move port I/O region request/release code into functions > 0a59a24e14e9 i2c: piix4: Move SMBus controller base address detect into function > fbafbd51bff5 i2c: piix4: Move SMBus port selection into function > 7c148722d074 i2c: piix4: Add EFCH MMIO support to region request and release > 46967bc1ee93 i2c: piix4: Add EFCH MMIO support to SMBus base address detect > 381a3083c674 i2c: piix4: Add EFCH MMIO support for SMBus port select > 6cf72f41808a i2c: piix4: Enable EFCH MMIO for Family 17h+ > abd71a948f7a Watchdog: sp5100_tco: Move timer initialization into function > 1f182aca2300 Watchdog: sp5100_tco: Refactor MMIO base address initialization > 0578fff4aae5 Watchdog: sp5100_tco: Add initialization using EFCH MMIO > 826270373f17 Watchdog: sp5100_tco: Enable Family 17h+ CPUs What is the overall diffstat of all of these commits applied? And why can't people with newer hardware just use 5.18 and newer releases like they do for other more complex hardware additions? thanks, greg k-h
