** Description changed: SRU Justification: [Impact] Support the I2C lock mechanism, otherwise there could be unexpected - behavior when the i2c driver is accessed by several entities like the - linux driver, ATF driver and UEFI driver. + behavior when an i2c bus is accessed by several entities like the linux + driver, ATF driver and UEFI driver. Replace ioremap_cache with ioremap + since it is deprecated in later kernels. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1981105 Title: i2c-mlxbf.c: support lock mechanism Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Replace ioremap_cache with ioremap since it is deprecated in later kernels. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1981105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
