Merge branch 'next' into 20251102-add-tinyusb-component

Author: kbx81

content/components/display/epaper_spi.md

@@ -15,28 +15,34 @@ better integration with ESPHome's async architecture.
 The communication method uses 4-wire [SPI](#spi), so you need to have an `spi:` section in your
 configuration.
 
+The driver supports a number of displays and there are also specific configurations for ESP32 boards with integrated displays.
+For those boards the predefined configuration will set the correct pins and dimensions for the display.
+
 ```yaml
 display:
   - platform: epaper_spi
-    cs_pin: GPIOXX
-    dc_pin: GPIOXX
-    busy_pin: GPIOXX
-    reset_pin: GPIOXX
-    model: 7.3in-spectra-e6
+    model: Seeed-reTerminal-E1002
     lambda: |-
       it.filled_circle(it.get_width() / 2, it.get_height() / 2, 50, Color::BLACK);
 ```
 
-## Configuration variables
+## Supported displays
 
-- **cs_pin** (**Required**, [Pin Schema](#config-pin_schema)): The CS pin.
-- **dc_pin** (**Required**, [Pin Schema](#config-pin_schema)): The DC pin.
-- **model** (**Required**): The model of the ePaper display. Currently supported:
+| Model name             | Manufacturer | Product Description                                        |
+|------------------------|--------------|------------------------------------------------------------|
+| Spectra-E6             | Eink         | <https://www.eink.com/brand/detail/Spectra6>               |
+| Seeed-reTerminal-E1002 | Seeed Studio | <https://www.seeedstudio.com/reTerminal-E1002-p-6533.html> |
+
+## Configuration variables
 
-  - `7.3in-spectra-e6` - 7.3" Spectra E6 6-color display (800×480 pixels)
+When using a model defining an integrated ESP32 display board most of the configuration such as the pins and dimensions will be set by default,
+but can be overridden if needed.
 
-- **busy_pin** (*Optional*, [Pin Schema](#config-pin_schema)): The BUSY pin. Defaults to not connected.
-- **reset_pin** (*Optional*, [Pin Schema](#config-pin_schema)): The RESET pin. Defaults to not connected.
+- **model** (**Required**): The model of the ePaper display. See the table above for options.
+- **cs_pin** (**Required**, [Pin Schema](#config-pin_schema)): The CS pin. Predefined for integrated boards.
+- **dc_pin** (**Required**, [Pin Schema](#config-pin_schema)): The DC pin. Predefined for integrated boards.
+- **busy_pin** (*Optional*, [Pin Schema](#config-pin_schema)): The BUSY pin, if used.
+- **reset_pin** (*Optional*, [Pin Schema](#config-pin_schema)): The RESET pin, if used.
   Make sure you pull this pin high (by connecting it to 3.3V with a resistor) if not connected to a GPIO pin.
 
 - **rotation** (*Optional*): Set the rotation of the display. Everything you draw in `lambda:` will be rotated

content/components/display/mipi_spi.md

@@ -29,7 +29,7 @@ boards and chips, but the driver is also designed to be customisable in YAML for
 ## Supported boards and driver chips
 
 The driver supports a number of display driver chips, and can be configured for custom displays. As well as support for
-driver chips, there are also specific configurations for several ESP32 boards with integrated displays. For tbose boards
+driver chips, there are also specific configurations for several ESP32 boards with integrated displays. For those boards
 the predefined configuration will set the correct pins and dimensions for the display.
 
 For custom displays, the driver can be configured with the correct pins and dimensions, and the driver chip can be

content/components/esp32.md

@@ -148,6 +148,10 @@ esp32:
 - **enable_idf_experimental_features** (*Optional*, boolean): Can be set to `true` to enable experimental features. Use of
   experimental features may cause instability or other issues.
 
+- **loop_task_stack_size** (*Optional*, int): Loop task stack size in bytes. Increase if experiencing stack overflow
+  errors (e.g., with complex code or deep recursion). Higher values reduce heap availability. Valid range is 8192-32768
+  bytes. Defaults to 8192 bytes.
+
 **LWIP Optimization Options (ESP-IDF only):**
 
 The following options are available under the `advanced` section when using the ESP-IDF framework to optimize

content/components/i2c.md

@@ -9,7 +9,7 @@ params:
 
 {{< anchor "i2c" >}}
 
-This component sets up the I²C bus for your ESP32 or ESP8266. In order for these components
+This component sets up the I²C bus for your ESP32, ESP8266, RP2040 or NRF52. In order for these components
 to work correctly, you need to define the I²C bus in your configuration. Please note the ESP
 will enable its internal 10kΩ pullup resistors for these pins, so you usually don't need to
 put on external ones. You can use multiple devices on one I²C bus as each device is given a
@@ -39,7 +39,8 @@ i2c:
   Defaults to `true`.
 
 - **frequency** (*Optional*, float): Set the frequency the I²C bus should operate on.
-  Defaults to `50kHz`. Values are `10kHz`, `50kHz`, `100kHz`, `200kHz`, ... `800kHz`
+  Defaults to `50kHz`. Default for NRF52 is `100kHz`. Values are `10kHz`, `50kHz`, `100kHz`, `200kHz`, ... `800kHz`.
+  NRF52 supports only `100kHz` and `400kHz`.
 
 - **timeout** (*Optional*, [Time](#config-time)): Set the I²C bus timeout.
   Defaults to the framework defaults (`100us` on `esp32` with `esp-idf`, `50ms` on `esp32` with `Arduino`,

content/components/lvgl/_index.md

@@ -501,162 +501,6 @@ on_...:
       border_color: 0x00FF00
 ```
 
-{{< anchor "lvgl-layouts" >}}
-
-### Layouts
-
-Layouts aim to position widgets automatically, eliminating the need to specify `x` and `y` coordinates to position each widget. This is a great way to simplify your configuration as it allows you to omit alignment options.
-
-The layout configuration options are applied to any parent widget or page, influencing the appearance of the children. The position and size calculated by the layout overwrites the *normal* `x`, `y`, `width`, and `height` settings of the children.
-
-Check out [Flex layout positioning](#lvgl-cookbook-flex), [Grid layout positioning](#lvgl-cookbook-grid) and [Weather forecast panel](#lvgl-cookbook-weather) in the Cookbook for examples which demonstrate how to automate widget positioning, potentially reducing the size of your device's YAML configuration, and saving you from lots of manual calculations.
-
-The `hidden`, `ignore_layout` and `floating` [flags](#lvgl-widget-flags) can be used on widgets to ignore them in layout calculations.
-
-#### Configuration variables
-
-- **layout** (*Optional*, dict): A dictionary describing the layout configuration:
-  - **type** (*Optional*, string): `FLEX`, `GRID` or `NONE`. Defaults to `NONE`.
-  - Further options from below depending on the chosen type.
-
-#### Flex
-
-The Flex layout in LVGL is a subset implementation of [CSS Flexbox](https://css-tricks.com/snippets/css/a-guide-to-flexbox/).
-
-It can arrange items into rows or columns (tracks), handle wrapping, adjust spacing between items and tracks and even handle growing the layout to make the item(s) fill the remaining space with respect to minimum/maximum width and height.
-
-**Terms used:**
-
-- *track*: the rows or columns *main* direction flow: row or column in the direction in which the items are placed one after the other.
-- *cross direction*: perpendicular to the main direction.
-- *wrap*: if there is no more space in the track a new track is started.
-- *gap*: the space between the rows and columns or the items on a track.
-- *grow*: if set on an item it will grow to fill the remaining space on the track. The available space will be distributed among items respective to their grow value (larger value means more space). It dictates what amount of the available space the widget should take up. For example if all items on the track have a `grow` set to `1`, the space in the track will be distributed equally to all of them. If one of the items has a value of 2, that one would take up twice as much of the space as either one of the others.
-
-**Configuration variables:**
-
-- **flex_flow** (*Optional*, string): Select the arrangement of the children widgets:
-- `ROW`  : place the children in a row without wrapping.
-- `COLUMN`  : place the children in a column without wrapping.
-- `ROW_WRAP`  : place the children in a row with wrapping (default).
-- `COLUMN_WRAP`  : place the children in a column with wrapping.
-- `ROW_REVERSE`  : place the children in a row without wrapping but in reversed order.
-- `COLUMN_REVERSE`  : place the children in a column without wrapping but in reversed order.
-- `ROW_WRAP_REVERSE`  : place the children in a row with wrapping but in reversed order.
-- `COLUMN_WRAP_REVERSE`  : place the children in a column with wrapping but in reversed order.
-
-- **flex_align_main** (*Optional*, string): Determines how to distribute the items in their track on the *main* axis. For example, flush the items to the right on with `flex_flow: ROW_WRAP` (known as *justify-content* in CSS). Possible options below.
-- **flex_align_cross** (*Optional*, string): Determines how to distribute the items in their track on the *cross* axis. For example, if the items have different height place them to the bottom of the track (known as *align-items* in CSS). Possible options below.
-- **flex_align_track** (*Optional*, string): Determines how to distribute the tracks (known as *align-content* in CSS). Possible options below.
-
-    Values for use with `flex_align_main`, `flex_align_cross`, `flex_align_track`  :
-
-- `START`  : means left horizontally and top vertically (default).
-- `END`  : means right horizontally and bottom vertically.
-- `CENTER`  : simply center.
-- `SPACE_EVENLY`  : items are distributed so that the spacing between any two items (and the space to the edges) is equal. Does not apply to `flex_align_track`.
-- `SPACE_AROUND`  : items are evenly distributed in the track with equal space around them. Note that visually the spaces aren't equal, since all the items have equal space on both sides. The first item will have one unit of space against the container edge, but two units of space between the next item because that next item has its own spacing that applies. Does not apply to `flex_align_track`.
-- `SPACE_BETWEEN`  : items are evenly distributed in the track: first item is on the start line, last item on the end line. Does not apply to `flex_align_track`.
-
-- **pad_row** (*Optional*, int16): Set the padding between the rows, in pixels.
-- **pad_column** (*Optional*, int16): Set the padding between the columns, in pixels.
-- **flex_grow** (*Optional*, int16): Can be used to make one or more children fill the available space on the track. When one or more children have `flex_grow` set, the available space will be distributed proportionally to the grow values. Defaults to `0`, which disables growing.
-
-```yaml
-# Example flex layout
-
-- obj:
-    layout:
-      type: flex
-      pad_row: 4
-      pad_column: 4px
-      flex_align_main: center
-      flex_align_cross: start
-      flex_align_track: end
-    widgets:
-      - animimg:
-          flex_grow: 1
-```
-
-#### Grid
-
-The Grid layout in LVGL is a subset implementation of [CSS Grid](https://css-tricks.com/snippets/css/complete-guide-grid//).
-
-It can arrange items into a 2D "table" that has rows or columns (tracks). The item(s) can span through multiple columns or rows. The track's size can be set in pixels, to the largest item of the track (`CONTENT`  ) or in "free units" to distribute the free space proportionally.
-
-**Terms used:**
-
-- *tracks*: the rows or the columns.
-- *gap*: the space between the rows and columns or the items on a track.
-- *free unit (FR)*: a proportional distribution unit for the space available on the track. It accepts a unitless integer value that serves as a proportion. It dictates what amount of the available space the widget should take up. For example if all items on the track have a `FR` set to `1`, the space in the track will be distributed equally to all of them. If one of the items has a value of 2, that one would take up twice as much of the space as either one of the others.
-
-Child widgets can be placed on the grid using the `grid_cell_row_pos` and `grid_cell_column_pos` configuration variables.
-If either is specified both must be specified. If neither is specified the widget will be placed in the first available position, in a row-major order.
-Row and column spans will be taken into account when reserving space.
-
-**Configuration variables (must be placed under the layout key):**
-
-- **grid_rows** (**Required**): The number of rows in the grid, expressed a list of values in pixels, `CONTENT` or `FR(n)` (free units, where `n` is a proportional integer value).
-- **grid_columns** (**Required**): The number of columns in the grid, expressed a list of values in pixels, `CONTENT` or `FR(n)` (free units, where `n` is a proportional integer value).
-- **grid_row_align** (*Optional*, string): How to align the row. Works only when `grid_rows` is given in pixels. Possible options below.
-- **grid_column_align** (*Optional*, string): How to align the column. Works only when `grid_columns` is given in pixels. Possible options below.
-- **pad_row** (*Optional*, int16): Set the padding between the rows, in pixels.
-- **pad_column** (*Optional*, int16): Set the padding between the columns, in pixels.
-
-In a grid layout, *all the widgets placed on the grid* can have some additional configuration variables to help with placement:
-
-- **grid_cell_row_pos** (*Optional*, int16): Position of the widget, in which row to appear (0 based count).
-- **grid_cell_column_pos** (*Optional*, int16): Position of the widget, in which column to appear (0 based count).
-- **grid_cell_x_align** (*Optional*, string): How to align the widget horizontally within the cell. Can also be applied through [Style properties](#lvgl-styling). Possible options below.
-- **grid_cell_y_align** (*Optional*, string): How to align the widget vertically within the cell. Can also be applied through [Style properties](#lvgl-styling). Possible options below.
-- **grid_cell_row_span** (*Optional*, int16): How many rows to span across the widget. Defaults to `1`.
-- **grid_cell_column_span** (*Optional*, int16): How many columns to span across the widget.. Defaults to `1`.
-
-> [!NOTE]
-> These `grid_cell_` variables are applied to individual widgets (cells) within the grid layout!
-
-Values for use with `grid_column_align`, `grid_row_align`, `grid_cell_x_align`, `grid_cell_y_align`  :
-
-- `START`  : means left horizontally and top vertically (default).
-- `END`  : means right horizontally and bottom vertically.
-- `CENTER`  : simply center.
-- `STRETCH`  : stretch the widget to the cell in the respective direction. Does not apply to `grid_column_align`, `grid_row_align`.
-- `SPACE_EVENLY`  : items are distributed so that the spacing between any two items (and the space to the edges) is equal.
-- `SPACE_AROUND`  : items are evenly distributed in the track with equal space around them. Note that visually the spaces aren't equal, since all the items have equal space on both sides. The first item will have one unit of space against the container edge, but two units of space between the next item because that next item has its own spacing that applies.
-- `SPACE_BETWEEN`  : items are evenly distributed in the track: first item is on the start line, last item on the end line.
-
-```yaml
-# Example grid layout
-
-- obj:
-    layout:
-      type: grid
-      grid_row_align: end
-      grid_rows: [25px, fr(1), content]
-      grid_columns: [fr(1), fr(1)]
-      pad_row: 6px
-      pad_column: 0
-    widgets:
-      - image:
-          grid_cell_row_pos: 0
-          grid_cell_column_pos: 0
-      - obj:
-          grid_cell_row_pos: 0
-          grid_cell_column_pos: 1
-      - obj:
-          grid_cell_row_pos: 2
-          grid_cell_column_pos: 0
-      - label:
-          text: "This will be placed in row 1, column 0"
-      - label:
-          text: "This will be placed in row 1, column 1"
-      - label:
-          text: "This will be placed in row 2, column 1, since 2/0 is occupied"
-```
-
-> [!TIP]
-> To visualize real, calculated sizes of transparent widgets you can temporarily set `outline_width: 1` on them.
-
 {{< anchor "lvgl-gradients" >}}
 
 ### Gradients