Skip to content
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

Multi d457 #11070

Merged
merged 2 commits into from Nov 9, 2022
Merged

Multi d457 #11070

merged 2 commits into from Nov 9, 2022

Conversation

hsuys
Copy link
Contributor

@hsuys hsuys commented Nov 4, 2022

Enabling multi camera support for D457

Copy link
Contributor

@remibettan remibettan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few comments - great work!

@@ -761,11 +761,12 @@ namespace librealsense
// next several lines permit to use D457 even if a usb device has already "taken" the video0,1,2 (for example)
// further development is needed to permit use of several mipi devices
static int first_video_index = ind;
if (ind == first_video_index || ind == first_video_index + 2 || ind == first_video_index + 4)
ind = (ind - first_video_index) % 6; // offset from first mipi video node and assume 6 nodes per mipi camera
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will not work if a usb device is also connected. It will have 3 video nodes and the logic used here will then not work.

@@ -784,7 +785,7 @@ namespace librealsense
// are not available via mipi
// TODO - find a way to assign unique id for mipi
// maybe using bus_info and card params (see above in this method)
//info.unique_id = busnum + "-" + devpath + "-" + devnum;
info.unique_id = bus_info; // use bus_info as per camera unique id for mipi
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to be enough, but could you please add here how would the busnum look like for each of the mipi devices, for example if 2 devices are connected?
Besides that, if this is chosen as unique_id, the above comment can be removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you.
Below is an example of busnum as well as the card param: [bus_info -- card_info] of 4 x D457 mipi devices. Bus_info seems to be unique to each mipi device and work in current system.

platform:15c10000.vi:0 -- vi-output, DS5 mux 34-0010
platform:15c10000.vi:0 -- 15c10000.vi-metadata-0
platform:15c10000.vi:0 -- vi-output, DS5 mux 35-0010
platform:15c10000.vi:0 -- 15c10000.vi-metadata-0
platform:15c10000.vi:0 -- vi-output, DS5 mux 36-0010
platform:15c10000.vi:0 -- vi-output, DS5 mux 37-0010

platform:15c10000.vi:2 -- vi-output, DS5 mux 38-0010
platform:15c10000.vi:2 -- 15c10000.vi-metadata-2
platform:15c10000.vi:2 -- vi-output, DS5 mux 39-0010
platform:15c10000.vi:2 -- 15c10000.vi-metadata-2
platform:15c10000.vi:2 -- vi-output, DS5 mux 40-0010
platform:15c10000.vi:2 -- vi-output, DS5 mux 41-0010

platform:15c10000.vi:4 -- vi-output, DS5 mux 42-0010
platform:15c10000.vi:4 -- 15c10000.vi-metadata-4
platform:15c10000.vi:4 -- vi-output, DS5 mux 43-0010
platform:15c10000.vi:4 -- 15c10000.vi-metadata-4
platform:15c10000.vi:4 -- vi-output, DS5 mux 44-0010
platform:15c10000.vi:4 -- vi-output, DS5 mux 45-0010

platform:15c10000.vi:5 -- vi-output, DS5 mux 46-0010
platform:15c10000.vi:5 -- 15c10000.vi-metadata-5
platform:15c10000.vi:5 -- vi-output, DS5 mux 47-0010
platform:15c10000.vi:5 -- 15c10000.vi-metadata-5
platform:15c10000.vi:5 -- vi-output, DS5 mux 48-0010
platform:15c10000.vi:5 -- vi-output, DS5 mux 49-0010

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems great. Thanks

@remibettan remibettan self-requested a review November 9, 2022 14:51
Copy link
Contributor

@remibettan remibettan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR can be merged.
Solution is not full, but it is better than current status.
@hsuys thanks a lot for your work!

@Nir-Az Nir-Az merged commit 44e8a80 into IntelRealSense:D4XX_MIPI Nov 9, 2022
dmipx added a commit to dmipx/librealsense that referenced this pull request Feb 1, 2023
Following DSO-18585 PR IntelRealSense#11070
For use with jp5-2d457-1-des

Signed-off-by: Dmitry Perchanov <dmitry.perchanov@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants