Skip to content

Conversation

@jeremydick
Copy link
Contributor

Set cs_is_gpio only if there is a GPIO CS, configure the CS as a native hardware CS if not

This fixes incorrectly trying to use a GPIO CS when there isn't one

@jeremydick
Copy link
Contributor Author

Failing CI test is due to #97379

Set cs_is_gpio only if there is a GPIO CS, configure the CS as
a native hardware CS if not

This fixes incorrectly trying to use a GPIO CS when there isn't one

Signed-off-by: Jeremy Dick <[email protected]>
@sonarqubecloud
Copy link

@diegoherranz
Copy link
Contributor

+1 to this PR
I use a MIPI DBI screen with hardware-controlled chip select which suffered this regression.
I've tested this PR and it fixes the regression successfully.

Thanks.

@cfriedt cfriedt merged commit 011a357 into zephyrproject-rtos:main Oct 14, 2025
26 checks passed
@zbianbiaos
Copy link

011a357 drivers: mipi-dbi-spi: fix initialization of SPI CS
I have a question regarding devices like the st7789. Previously, the corresponding SPI device was obtained through the "spi-dev" property of mipi-dbi, but now it seems problematic that it is no longer retrieved from spi-dev. I tested with my own custom board, and after merging this commit, my LCD no longer displays anything. Will there be any follow-up commits to address this issue? Or could this be a problem with my program?

@jeremydick
Copy link
Contributor Author

@zbianbiaos #98086 should address your issue

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.

6 participants