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

drivers: display: fix zero-buffers-in-SRAM case in DCNANO LCDIF #58879

Merged
merged 1 commit into from
Jun 15, 2023

Conversation

aedancullen
Copy link
Contributor

If CONFIG_MCUX_DCNANO_LCDIF_EXTERNAL_FB_MEM is not set and CONFIG_MCUX_DCNANO_LCDIF_FB_NUM is zero, a division by zero occurs. Use the same framebuffer size definition as in the external-framebuffer case to resolve this.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Hello @aedancullen, and thank you very much for your first pull request to the Zephyr project!

A project maintainer just triggered our CI pipeline to run it against your PR and ensure it's compliant and doesn't cause any issues. You might want to take this opportunity to review the project's Contributor Expectations and make any updates to your pull request if necessary. 😊

Copy link
Collaborator

@danieldegrasse danieldegrasse left a comment

Choose a reason for hiding this comment

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

Hi @aedancullen, thanks for the contribution! The CI pipeline seems to be flagging a compliance issue with your commit message. You need to insure that each line of the commit message body is no more than 75 characters long.

Also, this issue appears to be resolving a bug. The project is currently in a feature freeze state, so we can only merge PRs that explicitly link to a github issue, or make documentation updates.
I've created an issue to highlight this bug, if you add the following text to your commit message body:

Fixes #58908, then the issue should be linked.

@danieldegrasse
Copy link
Collaborator

It's also worth noting that when CONFIG_MCUX_DCNANO_LCDIF_EXTERNAL_FB_MEM=n, the user must manually enable CONFIG_MEMC if they plan to store framebuffers in the PSRAM present on the RT595 EVK, as without CONFIG_MCUX_DCNANO_LCDIF_EXTERNAL_FB_MEM=y the MEMC Kconfig will not be y-implied.

If CONFIG_MCUX_DCNANO_LCDIF_EXTERNAL_FB_MEM is not set and
CONFIG_MCUX_DCNANO_LCDIF_FB_NUM is zero, a division by zero occurs.
Use the same framebuffer size definition as in the external-framebuffer
case to resolve this.

Fixes zephyrproject-rtos#58908.

Signed-off-by: Aedan Cullen <[email protected]>
@nashif nashif merged commit 785d9bd into zephyrproject-rtos:main Jun 15, 2023
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Hi @aedancullen!
Congratulations on getting your very first Zephyr pull request merged 🎉🥳. This is a fantastic achievement, and we're thrilled to have you as part of our community!

To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge.

Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LCDIF DCNANO Build fails when external memory is disabled and no driver framebuffers are allocated
6 participants