Mirrors/libwebsockets
1
0
Fork 0
mirror of https://github.com/warmcat/libwebsockets.git synced 2025-03-16 00:00:07 +01:00
Code Issues Releases Wiki Activity
libwebsockets/lib/drivers/CMakeLists.txt

31 lines
667 B
Text
Raw Permalink Normal View History

drivers: initial generic gpio and i2c plus bitbang Make a start on generic peripheral and bus drivers to provide meta-functionality regardless of platform. On the one hand this simply provides... - bitbang i2c on top of esp-idf gpio apis - ssd1306 oled chip driver as found on Heltec WB32 - modifications to the minimal example test for esp32 to use that ... on the other hand, those capabilities are provided by creating: - an abstract i2c class object - an abstract gpio class object - i2c class implementation using the abstract gpio for bitbang - an abstract display class object - an abstract display state (brightness, animated change, on/off/init tracking, autodim after inactive, auto-off / blanking after inactive) ... with the intention, eg, you only have to add a platform implementation for the gpio to be able to use the i2c-based display drivers and state handling, and i2c bitbang, without any other modifications.
2020-06-10 19:17:08 +01:00
list(APPEND SOURCES
drivers/display/lws-display.c
drivers/display/ssd1306-i2c.c
esp32-wrover-kit Add lws_display and minimal example support for esp32-wrover to match wsp32-heltec-wb32 Since no usable buttons that don't affect something else on wrover kit, assumes a button to 0V on GPIO14.
2020-06-25 14:44:05 +01:00
drivers/display/ili9341-spi.c
drivers/i2c/lws-i2c.c
drivers: initial generic gpio and i2c plus bitbang Make a start on generic peripheral and bus drivers to provide meta-functionality regardless of platform. On the one hand this simply provides... - bitbang i2c on top of esp-idf gpio apis - ssd1306 oled chip driver as found on Heltec WB32 - modifications to the minimal example test for esp32 to use that ... on the other hand, those capabilities are provided by creating: - an abstract i2c class object - an abstract gpio class object - i2c class implementation using the abstract gpio for bitbang - an abstract display class object - an abstract display state (brightness, animated change, on/off/init tracking, autodim after inactive, auto-off / blanking after inactive) ... with the intention, eg, you only have to add a platform implementation for the gpio to be able to use the i2c-based display drivers and state handling, and i2c bitbang, without any other modifications.
2020-06-10 19:17:08 +01:00
drivers/i2c/bitbang/lws-bb-i2c.c
esp32-wrover-kit Add lws_display and minimal example support for esp32-wrover to match wsp32-heltec-wb32 Since no usable buttons that don't affect something else on wrover kit, assumes a button to 0V on GPIO14.
2020-06-25 14:44:05 +01:00
drivers/spi/lws-spi.c
drivers/spi/bitbang/lws-bb-spi.c
lws_button and lws_led Generic drivers for buttons and leds
2020-06-17 07:54:26 +01:00
drivers/button/lws-button.c
drivers/led/led-gpio.c
lws_pwm
2020-06-18 07:53:07 +01:00
drivers/led/led-seq.c
drivers/pwm/pwm.c
lws-settings
2020-06-29 09:31:21 +01:00
drivers/settings/settings.c
drivers: initial generic gpio and i2c plus bitbang Make a start on generic peripheral and bus drivers to provide meta-functionality regardless of platform. On the one hand this simply provides... - bitbang i2c on top of esp-idf gpio apis - ssd1306 oled chip driver as found on Heltec WB32 - modifications to the minimal example test for esp32 to use that ... on the other hand, those capabilities are provided by creating: - an abstract i2c class object - an abstract gpio class object - i2c class implementation using the abstract gpio for bitbang - an abstract display class object - an abstract display state (brightness, animated change, on/off/init tracking, autodim after inactive, auto-off / blanking after inactive) ... with the intention, eg, you only have to add a platform implementation for the gpio to be able to use the i2c-based display drivers and state handling, and i2c bitbang, without any other modifications.
2020-06-10 19:17:08 +01:00
)
lws_netdev: use lws_settings Perform the AP selection using lws_settings and a generic scan state machine
2020-07-02 15:38:53 +01:00
if (LWS_WITH_NETWORK)
list(APPEND SOURCES
drivers/netdev/netdev.c
drivers/netdev/wifi.c)
endif()
drivers: initial generic gpio and i2c plus bitbang Make a start on generic peripheral and bus drivers to provide meta-functionality regardless of platform. On the one hand this simply provides... - bitbang i2c on top of esp-idf gpio apis - ssd1306 oled chip driver as found on Heltec WB32 - modifications to the minimal example test for esp32 to use that ... on the other hand, those capabilities are provided by creating: - an abstract i2c class object - an abstract gpio class object - i2c class implementation using the abstract gpio for bitbang - an abstract display class object - an abstract display state (brightness, animated change, on/off/init tracking, autodim after inactive, auto-off / blanking after inactive) ... with the intention, eg, you only have to add a platform implementation for the gpio to be able to use the i2c-based display drivers and state handling, and i2c bitbang, without any other modifications.
2020-06-10 19:17:08 +01:00
if (LWS_ESP_PLATFORM)
list(APPEND SOURCES
lws_pwm
2020-06-18 07:53:07 +01:00
plat/freertos/esp32/drivers/gpio-esp32.c
plat/freertos/esp32/drivers/pwm-esp32.c
)
drivers: initial generic gpio and i2c plus bitbang Make a start on generic peripheral and bus drivers to provide meta-functionality regardless of platform. On the one hand this simply provides... - bitbang i2c on top of esp-idf gpio apis - ssd1306 oled chip driver as found on Heltec WB32 - modifications to the minimal example test for esp32 to use that ... on the other hand, those capabilities are provided by creating: - an abstract i2c class object - an abstract gpio class object - i2c class implementation using the abstract gpio for bitbang - an abstract display class object - an abstract display state (brightness, animated change, on/off/init tracking, autodim after inactive, auto-off / blanking after inactive) ... with the intention, eg, you only have to add a platform implementation for the gpio to be able to use the i2c-based display drivers and state handling, and i2c bitbang, without any other modifications.
2020-06-10 19:17:08 +01:00
endif()
exports_to_parent_scope()
Reference in a new issue Copy permalink