Hello. Yes, there was my bug in incorrectly merging commits for the i2c subsystem. This bug went away, but another one appeared when adding mux-adapter: ERROR: i2c4: failed to add mux-adapter (error=-16) ERROR: pca954x pca95460: failed to register multiplexed adapter0 чт, 12 дек. 2024 г. в 12:03, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > > Hi Alexander, > > On Wed, Dec 11, 2024 at 09:14:32AM +0300, Alexander Shiyan wrote: > > Hello. > > > > After updating barebox to version 2024.12.0, an error message appeared > > when loading > > the RK3568 board. Accordingly, the I2C1 interface does not work. > > In the previous version (2024.10.0), everything worked as it should. I did not > > understand what the problem is, but I suspect that aliases are now > > parsed incorrectly. > > The system has an alias i2c1 (this is the basic SOC i2c1 interface) > > and an alias i2c10 for the GPIO expander. Perhaps the problem is somewhere here? > > > > ERROR: rk3x-i2c fe5a0000.i2c@xxxxxxxxxxx: probe failed: Device or resource busy > > The culprit is likely somewhere in these commits: > > 79357f8b96 i2c: start dynamic I2C bus numbers at 32 > b474672545 i2c: get adapter.nr from device tree > 5b167ad520 i2c: set adapter.nr explicitly to -1 > > We now use of_alias_get_id() to get the i2c adapter nr. Which adapter > number does fe5a0000.i2c@xxxxxxxxxxx get and which i2c bus device has > already occupied that number? > > Sascha > > -- > Pengutronix e.K. | | > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
