<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Kernel Panic When Registering Custom Camera on i.MX8MP FRDM with Dual MIPI CSI-2 Cameras in i.MX Solutions</title>
    <link>https://community.nxp.com/t5/i-MX-Solutions/Kernel-Panic-When-Registering-Custom-Camera-on-i-MX8MP-FRDM-with/m-p/2392382#M745</link>
    <description>&lt;P&gt;Dear Support Team,&lt;/P&gt;&lt;P&gt;We are currently working on integrating two cameras using the i.MX8MP FRDM board.&lt;/P&gt;&lt;P&gt;The camera configuration is as follows:&lt;/P&gt;&lt;P&gt;* CSI2:0 is connected to an OV5640 camera.&lt;BR /&gt;* CSI2:1 is connected to a custom camera module.&lt;/P&gt;&lt;P&gt;For both cameras, we configured the device tree so that the image pipeline does not use ISP functionality. The intended pipeline is:&lt;BR /&gt;"Sensor → MIPI CSI-2 → ISI → Capture"&lt;/P&gt;&lt;P&gt;The device tree file is attached for your reference: "imx8mp-frdm-ov5640-cusdom.dts"&lt;/P&gt;&lt;P&gt;The issue is that the custom camera driver successfully completes the I2C probe process on I2C3, but a kernel panic occurs when calling "v4l2_async_register_subdev_sensor()".&lt;/P&gt;&lt;P&gt;In summary, the kernel panic occurs because "mxc_isi.1" has not been created or registered at the time when the custom camera is registered.&lt;/P&gt;&lt;P&gt;The related kernel panic log is attached: "panic-log.txt"&lt;/P&gt;&lt;P&gt;We have also attached the probe function implementation of the custom camera driver: "custom_driver_probe.c"&lt;/P&gt;&lt;P&gt;We created "imx8mp-frdm-ov5640-cusdom.dts" by referring to the default device tree configuration of the i.MX8MP FRDM board.&lt;/P&gt;&lt;P&gt;The OV5640 camera is working correctly. However, the custom camera cannot establish the connection with the ISI pipeline, which eventually causes the kernel panic.&lt;/P&gt;&lt;P&gt;After reviewing both the device tree configuration and the custom camera driver, we have not been able to identify the root cause of the issue.&lt;/P&gt;&lt;P&gt;The attached "imx8-media-dev.c" file only contains additional debug messages that we added to determine where the kernel panic occurs.&lt;/P&gt;&lt;P&gt;Our goal is to operate two different cameras simultaneously through the MIPI CSI-2 interfaces on the i.MX8MP platform.&lt;/P&gt;&lt;P&gt;Could you please review the attached device tree and driver code and advise which configuration or implementation part may be incorrect or missing?&lt;/P&gt;&lt;P&gt;Your support and guidance would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Seobi&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jul 2026 12:52:40 GMT</pubDate>
    <dc:creator>seobi</dc:creator>
    <dc:date>2026-07-08T12:52:40Z</dc:date>
    <item>
      <title>Kernel Panic When Registering Custom Camera on i.MX8MP FRDM with Dual MIPI CSI-2 Cameras</title>
      <link>https://community.nxp.com/t5/i-MX-Solutions/Kernel-Panic-When-Registering-Custom-Camera-on-i-MX8MP-FRDM-with/m-p/2392382#M745</link>
      <description>&lt;P&gt;Dear Support Team,&lt;/P&gt;&lt;P&gt;We are currently working on integrating two cameras using the i.MX8MP FRDM board.&lt;/P&gt;&lt;P&gt;The camera configuration is as follows:&lt;/P&gt;&lt;P&gt;* CSI2:0 is connected to an OV5640 camera.&lt;BR /&gt;* CSI2:1 is connected to a custom camera module.&lt;/P&gt;&lt;P&gt;For both cameras, we configured the device tree so that the image pipeline does not use ISP functionality. The intended pipeline is:&lt;BR /&gt;"Sensor → MIPI CSI-2 → ISI → Capture"&lt;/P&gt;&lt;P&gt;The device tree file is attached for your reference: "imx8mp-frdm-ov5640-cusdom.dts"&lt;/P&gt;&lt;P&gt;The issue is that the custom camera driver successfully completes the I2C probe process on I2C3, but a kernel panic occurs when calling "v4l2_async_register_subdev_sensor()".&lt;/P&gt;&lt;P&gt;In summary, the kernel panic occurs because "mxc_isi.1" has not been created or registered at the time when the custom camera is registered.&lt;/P&gt;&lt;P&gt;The related kernel panic log is attached: "panic-log.txt"&lt;/P&gt;&lt;P&gt;We have also attached the probe function implementation of the custom camera driver: "custom_driver_probe.c"&lt;/P&gt;&lt;P&gt;We created "imx8mp-frdm-ov5640-cusdom.dts" by referring to the default device tree configuration of the i.MX8MP FRDM board.&lt;/P&gt;&lt;P&gt;The OV5640 camera is working correctly. However, the custom camera cannot establish the connection with the ISI pipeline, which eventually causes the kernel panic.&lt;/P&gt;&lt;P&gt;After reviewing both the device tree configuration and the custom camera driver, we have not been able to identify the root cause of the issue.&lt;/P&gt;&lt;P&gt;The attached "imx8-media-dev.c" file only contains additional debug messages that we added to determine where the kernel panic occurs.&lt;/P&gt;&lt;P&gt;Our goal is to operate two different cameras simultaneously through the MIPI CSI-2 interfaces on the i.MX8MP platform.&lt;/P&gt;&lt;P&gt;Could you please review the attached device tree and driver code and advise which configuration or implementation part may be incorrect or missing?&lt;/P&gt;&lt;P&gt;Your support and guidance would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Seobi&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jul 2026 12:52:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Solutions/Kernel-Panic-When-Registering-Custom-Camera-on-i-MX8MP-FRDM-with/m-p/2392382#M745</guid>
      <dc:creator>seobi</dc:creator>
      <dc:date>2026-07-08T12:52:40Z</dc:date>
    </item>
  </channel>
</rss>

