Skip to content

IMX708: Add support for 4-lane operation #6775

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.

Sign up for GitHub

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

Open
wants to merge 7 commits into
base: rpi-6.12.y
Choose a base branch
from
+376 −125
Open

IMX708: Add support for 4-lane operation #6775

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
2d38887
imx708: intial support for 4-lane operation
peyton-howe Apr 2, 2025
0a886f7
Update pixel rate for 4lane full resolution and make HBLANK controllable
peyton-howe Apr 4, 2025
2e4be19
Rework imx708 driver to modify pixel rate and line length based on th…
peyton-howe Apr 5, 2025
9e77b99
Some minor cleanup to better match IMX415 structure for dynamic setti…
peyton-howe Apr 9, 2025
1fd4408
Add missing vblank back to set_framing_limits and minor cleanup of na…
peyton-howe Apr 9, 2025
f31864a
Back to unsigned int for line_length_pix
peyton-howe Apr 9, 2025
55c7b20
Restructure WIP
peyton-howe Jun 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions arch/arm/boot/dts/overlays/README
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2972,6 +2972,8 @@ Params: rotation Mounting rotation of the camera sensor (0 or
Compute Module (CSI0, i2c_vc, and cam0_reg).
link-frequency Allowable link frequency values to use in Hz:
450000000 (default), 447000000, 453000000.
4lane Enable 4 CSI2 lanes. This requires a Compute
Module (1, 3, 4, or 5) or Pi 5.


Name: interludeaudio-analog
Expand Down
17 changes: 17 additions & 0 deletions arch/arm/boot/dts/overlays/imx708-overlay.dts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,22 @@
};
};

fragment@201 {
target = <&csi_ep>;
__dormant__ {
data-lanes = <1 2 3 4>;
};
};

fragment@202 {
target = <&cam_endpoint>;
__dormant__ {
data-lanes = <1 2 3 4>;
link-frequencies =
/bits/ 64 <547000000>;
};
};

__overrides__ {
rotation = <&cam_node>,"rotation:0";
orientation = <&cam_node>,"orientation:0";
Expand All @@ -95,6 +111,7 @@
vcm = <&vcm_node>, "status",
<0>, "=4";
link-frequency = <&cam_endpoint>,"link-frequencies#0";
4lane = <0>, "+201+202";
Copy link
Contributor

Choose a reason for hiding this comment

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

It looks like there could be a confusing interaction between link-frequency and 4lane overrides, which both try to change <&cam_endpoint>/link-frequencies. The actual frequency may depend on the order in which the dtparams are given.

If that's the case, is there a cleaner way to do it that would always give priority to the link-frequency?

Copy link
Contributor

Choose a reason for hiding this comment

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

Sadly there isn't a way to set priorities on DT overrides.

What could be done is to add a fragment 203 which sets the link frequency for 2 lane mode. link-frequency then updates both 202 and 203, and 4lane disables 203 as well as enabling 201 and 202. At least that should give a consistent behaviour.

};
};

Expand Down
Loading