6487a2a663
Remove `SPI_NOR_IDLE_IN_DPD` to simplify the possible transition states in the `spi_nor` driver. This option was originally added 5 years ago when device runtime PM was in a much less mature state. I do not believe having a separate power management implementation for this one in-tree driver is in the interests of the project. The behaviour of `SPI_NOR_IDLE_IN_DPD` leads to extremly suboptimal behaviour in use cases where multiple small reads are performed sequentially, see #69588. Removal of this option does not break the behaviour of any existing applications, only increases current consumption in idle by ~10uA until device runtime PM is enabled. Signed-off-by: Jordan Yates <jordan@embeint.com>
23 lines
704 B
YAML
23 lines
704 B
YAML
sample:
|
|
name: SPI Flash Sample
|
|
tests:
|
|
sample.drivers.spi.flash:
|
|
tags:
|
|
- spi
|
|
- flash
|
|
filter: dt_compat_enabled("jedec,spi-nor") or dt_compat_enabled("st,stm32-qspi-nor")
|
|
or dt_compat_enabled("st,stm32-ospi-nor") or dt_compat_enabled("st,stm32-xspi-nor")
|
|
or (dt_compat_enabled("nordic,qspi-nor") and CONFIG_NORDIC_QSPI_NOR)
|
|
platform_exclude: hifive_unmatched
|
|
harness: console
|
|
harness_config:
|
|
type: multi_line
|
|
ordered: true
|
|
regex:
|
|
- "Test 1: Flash erase"
|
|
- "Flash erase succeeded!"
|
|
- "Test 2: Flash write"
|
|
- "Attempting to write 4 bytes"
|
|
- "Data read matches data written. Good!!"
|
|
depends_on: spi
|