https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi?h=ti-linux-6.12.y&id=b8abee38c8362b6708e638dc01d8788f69afdf2b 

The commit above takes the interrupt line that is used for the JPEG Encoder on J722s. It's fine when AM62p is being used because JPEG Encoder isn't on that platform so the interrupt goes unused.  This patch has been added as a hack to git rid of issue and let JPEG Encoder use the interrupt on J722s (https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/arch/arm64/boot/dts/ti?h=ti-linux-6.12.y&id=e48de317af8546000492798f21ac29cd5361b802).

But, the JPEG Encoder J722s patch is now going to be upstream. And the AM62p patch is not upstream. I am requesting that another interrupt is found so that we don't have to carry a hack patch for J722s JPEG Encoding to work.

Customer: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1582808/am67a-irq-collision-between-pinctrl-and-e5010-jpec-encoder

Fix:

https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/arch/arm64/boot/dts/ti?h=ti-linux-6.12.y&id=4228a4b3351781f6c0d88e3b2047f62188279eff
https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi?h=ti-linux-6.12.y&id=a4d7dcd55304001db2f70268562d12017aae2527