> > > Maybe you think that MT8183 SoC only has the I3C controllers. Actually, > > > there are I2C and I3C controllers on MT8183 SoC. We will remove > > > "mediatek,share-i3c" for I2C controller driver, so these patches are > > > just to support the I2C controllers on MT8183 SoC. For the I3C > > > controller we will send some new patches which are based on i3c > > > framework directories(kernel/drivers/i3c), not based on > > > i2c-mt65xx.c. > > > > Sounds perfect to me. If it turns out that the I3C driver can share > > things with the I2C driver, we can discuss it then. But unless we have > > an I3C driver and know for sure, the above strategy seems good to me. > > > > Can I push the V4 patches of I2C controller driver now? or you just want > an I3C driver that is compatible with the I2C controller? If the V4 series does not use the "mediatek,share-i3c" binding anymore, please resend it. From what I recall, it should be OK then. > According to our plan, I2C controller will use > i2c-mt65xx.c(kernel/drivers/i2c/busses/)and I3C controller will use > i3c-xxx.c(kernel/drivers/i3c/master/) Sounds OK from what I understood. The I2C fallback from I3C will be interesting.
Attachment:
signature.asc
Description: PGP signature
