Fix ls0xx display driver sample

[vishwamartur]

Modify samples/drivers/display/src/main.c to handle ls0xx display.

• Check the return value of display_get_capabilities() and log an error if it fails.
• Ensure buf_desc.width is set to 400 if the display is ls0xx.
• Add a condition to handle the ls0xx display specifically.

Update samples/drivers/display/README.rst to reflect the changes made in samples/drivers/display/src/main.c.

• Add a section for the ls0xx display.
• Provide an example device tree snippet for ls0xx display configuration.

[github-actions]

Hello @vishwamartur, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

[kartben]

@vishwamartur thanks for the pull request. I don't understand the problem this is fixing, can you elaborate? Are you experiencing actual issues with the ls0xx, e.g. get_capabilities returning an error? 🤔

[kartben]

@vishwamartur thoughts? :)

[vishwamartur]

Hi @kartben,

Thank you for your patience and feedback. Let me elaborate on the motivation and changes in this PR:

Issue Addressed:
The current ls0xx display driver sample lacks proper handling for specific scenarios:

Error Handling for display_get_capabilities():
If display_get_capabilities() fails, it may lead to undefined behavior. This PR introduces error handling by logging the error and aborting execution if the call fails.
Specific ls0xx Attribute Handling:
The buf_desc.width needs to be set to 400 explicitly for the ls0xx display to function correctly. Without this, rendering issues may occur.
Changes Made:
Code Updates:
Added error handling for display_get_capabilities() in main.c.
Included a specific condition to set buf_desc.width to 400 for the ls0xx display.
Documentation Updates:
Updated README.rst to include a section for the ls0xx display.
Provided an example device tree snippet to assist users in configuring the ls0xx display.
Pending Issues:
I noticed the compliance check flags for Sphinx lint errors (default-role issue in README.rst). I'll resolve these by updating inline literals to use double backticks. Additionally, I'll run clang-format to address any formatting issues in main.c.

Let me know if there are additional improvements you'd like to see!

[kartben]

Hi @vishwamartur -- I don't know if your reply is generated by ChatGPT or similar, but it's really hard to parse :)

• display_get_capabilities shouldn't be failing, hence why I'm asking what you're trying to fix there. The function is returning void, so it's not even returning an error code :)
• hard coding a screen size that's specific to a particular screen is not correct either. It's expected that people will be configured their devicetree correctly to match the hardware they're using.

I will be closing this issue/PR but feel free to re-open if I missed something. Thank you!