So I checked the code and it seems that one value is missing on the device tree. I check the git log for this specific commit and I can see any changes related to DRM.
I understand that’s not a big deal, just a warning, but I wonder what I can do in my dts to avoid those kind of message ?
Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
The warning messages you’re encountering in the DRM (Direct Rendering Manager) subsystem on TorizonOS 6.6.1 with your Verdin iMX8M Plus module are related to the DRM core’s mode setting infrastructure. These warnings typically occur due to issues in the device tree configuration or the DRM driver’s handling of certain properties or objects.
Given the specific warnings about drm_mode_object_add and drm_object_attach_property, it seems there might be a discrepancy or an incomplete configuration related to the display setup in the device tree. The warnings suggest an issue with attaching properties to a DRM mode object, which could be due to missing or incorrectly specified properties for the display or its interfaces.
To address these warnings, you should:
Review the Device Tree: Ensure that the device tree entries for your display subsystem (LCDIF, LDB, or any other display interface you’re using) are correctly defined. Pay special attention to the properties related to panel orientation, mode settings, and any custom properties that your display setup might require.
Check for Missing Properties: The warning about drm_object_attach_property suggests that there might be an attempt to attach a property to a DRM object that hasn’t been properly initialized or defined. Make sure that all required properties for your display components are included in the device tree.
Update and Compare Device Trees: If you have a working setup with a previous version of TorizonOS (like 6.5.0, where you didn’t see these warnings), compare the device tree files between the two versions. Look for any changes or missing entries related to the display subsystem.
DRM Driver Review: Although you mentioned not seeing relevant changes in the git log, it might be helpful to review the DRM driver’s code for handling of properties and mode setting for your specific display setup. There could be changes in the DRM core or the i.MX-specific DRM driver that affect how properties are handled.
Kernel Configuration: Ensure that your kernel configuration includes all necessary options for DRM and the specific display interfaces you’re using. Missing kernel configuration options could lead to incomplete initialization of the DRM subsystem.
Debugging: Enable dynamic debug for DRM to get more detailed logs that might help pinpoint the issue. You can do this by adding drm.debug=0x1e log_buf_len=1M to the kernel command line. This will provide verbose DRM logs that could offer more insights into what’s causing the warnings.
Since these warnings
Please, also check if these links can help you solve your problem:
I don’t see the same warning using our LVDS display or an HDMI port.
Which display are you using in your product?
From your logs it seems you are using a custom device tree. Are there any display-related changes in it?
Also, are you using device tree overlays?
Yes I’m using a custom dts, based on the Verdin-WiFi. I added the LVDS display and other stuff related to the product. And I don’t have any overlays.
As the Bot suggested, I checked if the device tree from the Verdin changed with the new branch but nothing display related.
It was intended to fix some issues related to hot-plug on HDMI, but maybe it is causing the warning on your setup.
Can you try to revert the changes of this commit and see if the warning is still present?
It only changes a device tree file, so TorizonCore Builder will be enough to do this.
I did some more investigation into this and I was able to get similar error messages when I set back-porch values at 0 in the device tree.
It is worth noting that the errors also occurred with Torizon Os 6.5.0, so this may not be the same problem as you have here.
From the device tree you sent, I see that both back-porch values are set to 0, do you know if this is really required for your display?
A possible solution would be to move some of the front-porch cycles to the back-porch, maintaining the overall frequency.
For example:
I was able to reproduce the drm_mode_object_add error message.
What causes it is the screen rotation (rotation = <270>;) under the panel_lvds node.
I also see this error on Torizon OS 6.5.0, so it is unclear why it only manifests in Torizon OS 6.6.1 for you.
This configuration is most likely needed, so removing it is not really an option.
Considering the screen is working as expected, it should be safe to ignore it for now.
I will report this error message to the R&D team, as it indicates there is an actual issue that may create problems with other use cases.
We were able to reproduce the issue on the Linux BSP, therefore it is not unique to Torizon OS.
For this reason, the issue should be published on the Linux BSP Issue Tracker.
