ISI Channel busy when use Maxim 9286

[jack-cap]

Hi NXP,

      When I use Maxim 9286 cameras on IMX8QM Android Platform, I found that the ISI Channel[0] busy problem. so the video0 of Maxim 9286 can't work.  the kernel the following error:

[   10.791356] [VPU Encoder]     enable mu for core[0]
[   10.803557] [VPU Encoder]     vpu encoder core[0] firmware version is 1.2.2
[   10.829160] type=1400 audit(1578477204.112:56): avc: denied { write } for pid=2074 comm="Binder:2074_2" name="uevent" dev="sysfs" ino=21342 scontext=u:r:vold:s0 tcontext=u:object_r:sysfs_block_devices:s0 tclass=file permissive=0
[   10.849572] type=1400 audit(1578477205.020:551): avc: denied { read } for pid=2160 comm="HwBinder:2160_1" name="u:object_r:ffs_prop:s0" dev="tmpfs" ino=8864 scontext=u:r:hal_usb_impl:s0 tcontext=u:object_r:ffs_prop:s0 tclass=file permissive=0
[   10.877862] YYJ ADD test 1 hpd status=1 cable connected
[   10.878431] (null): mxc_isi_capture_open: ISI channel[0] is busy
[   10.910499] i.mx8-hdp 56268000.hdmi: 0,ff,ff,ff,ff,ff,ff,0
[   10.916271] YYJ ADD test 1 hpd status=1 cable connected
[   10.948157] i.mx8-hdp 56268000.hdmi: 0,ff,ff,ff,ff,ff,ff,0
[   10.954184] YYJ ADD test 1 hpd status=1 cable connected
[   10.986147] i.mx8-hdp 56268000.hdmi: 0,ff,ff,ff,ff,ff,ff,0
[   11.751903] [drm] phy_cfg_hdp() num_lanes: 4, mode:1920x1080p60, color depth: 8-bit, encoding: 1
[   11.760905] [drm] Pixel clock frequency (148500 kHz) is supported in this color depth (8-bit). Settings found in row 2
[   11.771656] [drm] Character clock frequency: 148500 kHz.
[   11.777013] [drm] VCO frequency (2970000 kHz) is supported. Settings found in row 25
[   11.799982] [drm] CDN_API_General_Write_Register_blocking LANES_CONFIG ret = 0
[   11.869260] android_work: sent uevent USB_STATE=CONNECTED
[   11.890724] configfs-gadget gadget: high-speed config #1: b
[   11.907410] android_work: sent uevent USB_STATE=CONFIGURED
[   11.956148] capability: warning: `main' uses 32-bit capabilities (legacy support in use)
[   12.921310] init: processing action (vendor.all.system_server.start=1) from (/vendor/etc/init/hw/init.freescale.rc:112)

Any help to solve this problem will be highly appreciated.

 Best Regards

[igorpadykov]

Hi yingjin

probably old chip revision was used in the case,

recommended to recheck that latest i.MX8QM silicon revision and

BSP used available on link: i.MX Software and Development Tools | NXP 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[jack-cap]

Hi igor

Recently,our build chip version is Android P9.0.0_2.1.1_AUTO (4.14.98 kernel) 

build info as below:

source build/envsetup.sh

lunch mek_8q_car2-userdebug

make 

Is there any other solutions  for this case ?

BRs

thanks

[igorpadykov]

had you verified that latest silicon revision with suffix "AB" used

in the case: Table 2. i.MX 8QuadMax Orderable part numbers

i.MX 8QuadPlus Automotive and Infotainment Applications Processors

Best regards
igor

[jack-cap]

Hi igor

Looking forward to your reply about isi busy question 

[igorpadykov]

>   Is there any differences between PIMX8QM6AVUFFAB and MIMX8QP6AVUFFAB

yes MIMX8QP6AVUFFAB is production part recommended for use in customer designs.

regarding " isi busy question " suggest to reproduce issue on i.MX8QM MEK reference board

with Demo Images from link:

i.MX Software and Development Tools | NXP 

Best regards
igor

[jack-cap]

hello
how to use vpu/gpu encode video stream on imx8qm android p os, such as webtrc.thanks

[jack-cap]

Hi  igor

On channel 0 busy           

   At present, we use the mx8_v4l2_cap_drm.c file under the imx8_v4l2_test directory to compile binary files and open the 4 way camera.there is no channel 0 busy issue. Using our own app to open will cause the problem of channel 0 busy,

   The only difference between the two way is that the camera will go through the Android Hal layer.           

   This is the issue of  Hardware or software? Do you have any other suggestions ?

   Hope your reply.

BRs

thanks

[jack-cap]

Hi igor

    Out silicon revision is PIMX8QM6AVUFFAB

    The model of the link you recommend is a little different from ours.

    Is there any differences between PIMX8QM6AVUFFAB and MIMX8QP6AVUFFAB

BRs

thanks

the info as below: