-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
LCD SPI Bus quad data support. (IDFGH-13741) #14605
Comments
Hi @kdschlosser The quad SPI LCD IO support was added in 20ebcf7 I believe we need to update the docs to reflect that. Thanks for the report! You can check out SPD2010 as an example of how to initialize QSPI LCD. |
Just out of question. is there a reason why this setting is not automatically set by checking the bus that was created to see if the data2 and data3 pins were set and if they are then set the quad marker? |
Good suggestion. @kdschlosser I think it's doable! |
I think it should be. You should be able to pull the information using the supplied host. same goes for octal. That would remove the need for those 2 "flags". It is also a way to ensure the user has actually has set the needed pins in order for it to work, |
Just out of question... There would only be one scenario where having that flag would serve a purpose. That scenario is if the display doesn't use quad but the user has some other device attached to the bus that does use quad. IDK if you can do that or not. Can a quad SPI bus be created and there is a quad SPI LCD display attached it that bus and also a normal SPI touch panel? Can the bus be bot quad and standard at the same time?? It would be something that i would not see happening all that often where the display would be standard attached to a quad bus, but it could happen... That is if it is even supported by the ESP-IDF.... |
Answers checklist.
General issue report
The documentation for version 5.2.2 states that the esp_lcd component using SPI that quad data is not supported. Is the documentation correct when it states this? If it is what does the timeline look like for adding that feature?
If the documentation is not correct (docs need updating) and it is supported is there anything else that needs to be done for it to work properly?
The text was updated successfully, but these errors were encountered: