zephyr/tests/drivers/disk/disk_access
Daniel DeGrasse 07a8e3253a drivers: disk: mmc_subsys: remove CONFIG_MMC_VOLUME_NAME
Remove CONFIG_MMC_VOLUME_NAME, and set the disk name based on the
``disk-name`` property. This aligns with other disk drivers, and allows
for multiple instances of the mmc_subsys disk driver to be registered.

Add disk-name properties for all in tree definitions for the
mmc-subsys disk driver, and change all in tree usage of the disk name

Fixes #75004

Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
2024-11-05 15:25:10 -06:00
..
boards tests/drivers disk_access: Switch from native_posix to native_sim 2024-08-16 11:20:34 +01:00
src drivers: disk: mmc_subsys: remove CONFIG_MMC_VOLUME_NAME 2024-11-05 15:25:10 -06:00
CMakeLists.txt
Kconfig
prj.conf
README.txt
testcase.yaml tests/drivers disk_access: Switch from native_posix to native_sim 2024-08-16 11:20:34 +01:00

Disk Access Test
##################

This test is intended to verify the functionality of disk devices in Zephyr.
It is designed to test the NXP USDHC disk driver, but can be used for other
disk devices as well. The test has the following phases:

* Setup test: Verifies that disk initialization works, as well as testing
  disk_access_ioctl by querying the disk for its sector size and sector count.
  Note that this test also verifies the memory buffers reserved for read/write
  tests are sufficiently large, and will fail if they are not (in which case
  the value of SECTOR_SIZE must be increased)

* Read test: Verifies that the driver can consistently read sectors. This test
  starts by reading sectors from a variety of start locations. Each location is
  read from several times, each time with a different number of desired sectors.
  The test deliberately will read sectors beyond the end of the disk, and if
  the driver does not reject this read request the tests will fail. Following
  these sector reads, the driver will read multiple times from the same memory
  location, to verify that the data being returned is the same.

* Write test: Verifies that the driver can consistently write sectors. This test
  follows the same flow as the read test, but at each step writes data to the
  disk and reads it back to verify correctness. The test first performs writes
  of various length to various sectors (once again, the driver must reject
  writes that would be outside the bounds of the disk), then performs multiple
  writes to the same location.