-
Notifications
You must be signed in to change notification settings - Fork 5.2k
arm64: dts: Sort out CM5 and I/O board I2C ports #6441
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
// SPDX-License-Identifier: GPL-2.0 | ||
|
||
i2c_csi_dsi0: &i2c0 { // Note: For CAM0 and DISP0 connectors | ||
}; | ||
|
||
i2c_csi_dsi1: &i2c6 { // Note: For CAM1, DISP1, on-board RTC, and fan controller | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And seeing as CAM1 and DISP1 share an I2C port, if the above is true about the MIPI wiring, that means we can't run two identical cameras or displays on CM5 with CM4IO (fine on CM5IO). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I believe that's correct. |
||
pinctrl-0 = <&rp1_i2c6_38_39>; | ||
pinctrl-names = "default"; | ||
clock-frequency = <100000>; | ||
symlink = "i2c-6"; | ||
}; | ||
|
||
i2c_csi_dsi: &i2c_csi_dsi1 { }; // The connector that needs no jumper to enable | ||
|
||
&aliases { | ||
/delete-property/ i2c11; | ||
i2c10 = &i2c_csi_dsi; | ||
}; | ||
|
||
// The RP1 USB3 interfaces are not usable on CM4IO | ||
|
||
&rp1_usb0 { | ||
status = "disabled"; | ||
}; | ||
|
||
&rp1_usb1 { | ||
status = "disabled"; | ||
}; |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
// SPDX-License-Identifier: GPL-2.0 | ||
|
||
i2c_csi_dsi1: &i2c0 { // Note: This is for CAM/DISP 1 connector | ||
symlink = "i2c-11"; | ||
}; | ||
|
||
i2c_csi_dsi0: &i2c6 { // Note: This is for CAM/DISP 0 connector | ||
pinctrl-0 = <&rp1_i2c6_38_39>; | ||
pinctrl-names = "default"; | ||
clock-frequency = <100000>; | ||
symlink = "i2c-6"; | ||
}; | ||
|
||
i2c_csi_dsi: &i2c_csi_dsi0 { }; // The connector that needs no jumper to enable |
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.
I haven't looked at the pinout, but CM5 only has 2 MIPI PHY ports, so do CAM0 and DISP0 actually connect to anything other than the I2C?
I'm sure Dominic made a comment in passing yesterday that CAM0 and DISP0 pins on the CM were repurposed for USB3.
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 is the connectivity table I ended up with:
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 means that CAM0 and DISP0 are not usable for cameras or displays, which is the better of the two options because that I2C port is effectively shared with ID_SC and ID_SD. The
i2c_csi_dsi0
parameter is there for compatibility with any existing I2C setup.i2c_csi_dsi1
(and its aliasi2c_csi_dsi
) is assigned to CAM1 and DISP1.