linux-next: regression in i2c-imx-lpi2c.c after rust-i2c-next merge (next-20260910)

From: Carlos Song <hidden>
Date: 2026-09-14 03:28:32
Also in: imx, linux-i2c, lkml

Hi, Mark and Andi

While looking at next-20260910, I noticed that the merge commit:

commit 2edfbdfb8f9c5b2482232087a03fa1a6692b9e5b
Merge: 98d87b29bc8a7 61ddec70c9bcc
Author: Mark Brown [off-list ref]
Date:   Thu Sep 10 14:19:17 2026 +0100

    Merge branch 'rust-i2c-next' of https://github.com/ikrtn/rust-for-linux

    # Conflicts:
    #       drivers/i2c/busses/i2c-imx-lpi2c.c

After this merge, I meet a regression on the i.MX8Q series starting from next-20260910
(next-20260909 was still fine).

The root cause is:
Change to lpi2c_imx_probe() from this patch[1] was replaced back with the old logic during the merge conflict resolution(2edfbdfb8f9c).

Could you help pick these missing codes back?

[1] 27c9445be86b1 i2c: imx-lpi2c: avoid accessing target registers on master-only controllers

Best Regards,
Carlos


NXP Public
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help