Implement data driven wear leveling (#21906)
* DD encoder map, wear leveling * remove encoder map from DD let's avoid the support headache * wear leveling: specify the allowed drivers by name Co-authored-by: Ryan <fauxpark@gmail.com> * Add additional params * Relocate under eeprom * disable parsing --------- Co-authored-by: Dimitris Mantzouranis <d3xter93@gmail.com> Co-authored-by: Ryan <fauxpark@gmail.com>
This commit is contained in:
parent
a03de8440b
commit
5fab310e65
4 changed files with 25 additions and 1 deletions
|
@ -202,6 +202,13 @@ Configures the [EEPROM](eeprom_driver.md) driver.
|
|||
* `driver`
|
||||
* The EEPROM backend to use. Must be one of `custom`, `i2c`, `legacy_stm32_flash`, `spi`, `transient`, `vendor`, `wear_leveling`.
|
||||
* Default: `"vendor"`
|
||||
* `wear_leveling`
|
||||
* `driver`
|
||||
* The driver to use. Must be one of `embedded_flash`, `legacy`, `rp2040_flash`, `spi_flash`, `custom`.
|
||||
* `backing_size`
|
||||
* Number of bytes used by the wear-leveling algorithm for its underlying storage, and needs to be a multiple of the logical size.
|
||||
* `logical_size`
|
||||
* Number of bytes “exposed” to the rest of QMK and denotes the size of the usable EEPROM.
|
||||
|
||||
## Encoder :id=encoder
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue