-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Add support for camera on i.MX RT11XX #69810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for camera on i.MX RT11XX #69810
Conversation
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
Hi @danieldegrasse , @decsny , @DerekSnell, could you please advise on the naming of the MIPI CSI-2 Rx driver ? Currently, I named it "mipi_csi2rx_nxp" because I remembered @DerekSnell has said that :
@decsny also proposed "CONFIG_VIDEO_MCUX_MIPI_CSI2RX". I think it is correct too. But frankly, I am a bit confused between "mcux" and "imx" (imx seems covers both mcu and mpu ?). So, I hesitated too much. Is it ok for you if we name them as below ?
Thanks |
MCUX refers to the MCUX-SDK. Which can theoretically have any kind of device in it, it's just a software ecosystem. IMX refers to the IMX MPU family. For the IMX MCU (RT family), they are called by IMXRT. (see soc/nxp folder). |
Update documents and tests to support the i.MX RT1170 EVK, the video test pattern generator and the new camera shields. Signed-off-by: Phi Bang Nguyen <[email protected]>
Add entry for ov5640 and add mimxrt1170_evk to the test platforms Signed-off-by: Phi Bang Nguyen <[email protected]>
Enable video feature on cm7 evk and evkb which are tested with ov5640 camera. Signed-off-by: Phi Bang Nguyen <[email protected]>
@danieldegrasse I updated the PR which addressed all of your comments in my possibility (for some comments that I cannot make the changes, I left my arguments). @loicpoulain , @danieldegrasse , @dleach02 : Really need your helps to make this PR moving forward as it has been here for quite a while. Thanks ! |
@ngphibang could you split this PR in different logical PRs (like one for misc fixes, one for new camera driver, etc...), it will be easier for you to have them reviewed and integrated. |
@loicpoulain Okay, I will do it. But the problem is the next PR will depend on all previous PRs and Zephyr requires that each commit / PR is bisectable and buildable. Would you mind if I include all the commits of the previous PRs into another PR ? For example : PR 1 |
@loicpoulain The first 3 splitted PRs which are independent each others are pushed. |
|
||
if (!bpp || ep != VIDEO_EP_OUT) { | ||
return -EINVAL; | ||
} | ||
|
||
data->pixelformat = fmt->pixelformat; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be deleted from video_mcux_csi_data
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, this commit can be squashed with the previous commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is addressed and merged.
@@ -1230,3 +1230,7 @@ | |||
*/ | |||
status = "disabled"; | |||
}; | |||
|
|||
zephyr_cam_i2c: &lpi2c6 {}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems board specific and probably belongs in the board overlay file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, it is pointed out by Daniel and I addressed it in the split PR.
csi_ep_in: endpoint { | ||
remote-endpoint = <&mt9m114_ep_out>; | ||
}; | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to add the labels related to the new shield you have created for 1064?
@mmahadevan108 : Thank you for your reviews ! But this PR is split into smaller one as requested by Loic. Could you review them instead ? I don't know if we can add a label "do not review" or "stale" or something like that on this PR ? |
@@ -7,9 +7,8 @@ | |||
Description | |||
*********** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has this been tested in 1064_evk after the changes to the sample? Do we need a boards overlay file for 1064_evk?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, it's tested. The board overlay for 1064 evk is in the same PR.
@ngphibang is this PR still needed? My understanding was that all the components of this PR had been split into smaller PRs. If we don't need this one open, let's go ahead and close it out to avoid additional review noise |
I thought that we should keep it as a reference and just close it when all the split PRs merged. |
Close to avoid additional review noise |
No worries- just don't want anyone reviewing the enablement to get confused by this PR :) |
This PR adds support to enable camera on i.MX RT11XX series. It adds