lovyan03 / LovyanGFX

SPI LCD graphics library for ESP32 (ESP-IDF/ArduinoESP32) / ESP8266 (ArduinoESP8266) / SAMD51(Seeed ArduinoSAMD51)
Other
1.03k stars 189 forks source link

Add support for QSPI bus in ESP32-S3? #467

Closed zeroomega closed 5 months ago

zeroomega commented 6 months ago

Carefully written requests are more likely to be given priority. 丁寧に記述された要望は優先して対応される可能性が高くなります。

As the title suggested, is it feasible to support the QSPI bus in ESP32-S3 platform? Right now under "src/lgfx/v1/platforms/esp32" there is only regular SPI bus support. It won't work with a QSPI bus.

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I have been using LovyanGFX on Lilygo T-Display-S3 with great success. However their newer display boards like "T-Display-S3 AMOLED"(https://www.lilygo.cc/products/t-display-s3-amoled) and "Lilygo T-Display-S3-Long"(https://www.lilygo.cc/products/t-display-s3-long) started to use QSPI bus between the MCU and display IC. I was trying to add support of QSPI bus and their display ICs to my local LovyanGFX fork but I discovered that the SPI bus code for ESP32 in your code base is using the low level ESP32 HAL functions instead of the regular ESP-IDF APIs. I don't have a lot of knowledge about low level HAL of ESP32 platform so I cannot add QSPI support by my own.

Describe the solution you'd like A clear and concise description of what you want to happen.

A supported QSPI bus implementation under "src/lgfx/v1/platforms/esp32" or "src/lgfx/v1/platforms/esp32S3"

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Maybe provide a common interface that allows the bus implementation to be done in user's code (outside of LovyanGFX) so ESP-IDF APIs can be easily used.

Additional context Add any other context or screenshots about the feature request here.

github-actions[bot] commented 5 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 5 months ago

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.