zephyr/tests/drivers/sdhc
Daniel DeGrasse 2be937dca4 tests: drivers: sdhc: setup SDHC IO before test
Rather than relying to the alphanumeric test ordering implemented in
ZTEST to ensure certain tests run first, setup the SDHC IO properties to
known good values before starting any of the tests. This allows the SDHC
tests to run in any order, rather than needing certain tests to run
first.

Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
2024-05-16 09:18:07 +02:00
..
src tests: drivers: sdhc: setup SDHC IO before test 2024-05-16 09:18:07 +02:00
CMakeLists.txt
prj.conf tests: remove CONFIG_ZTEST_NEW_API in all tests 2023-10-20 15:04:29 +02:00
README.txt
testcase.yaml samples, tests: convert string-based twister lists to YAML lists 2023-05-10 09:52:37 +02:00

SDHC API Test
##################

This test is designed to verify the functionality of a device implementing the
SD host controller API. It requires that an SD card be present on the SD bus
to pass. The test has the following phases:

* Reset test: Verify the SDHC can successfully reset the host controller state.
  This primarily tests that the driver returns zero for this call, although if
  the reset left the SDHC in a bad state subsequent tests may fail.

* Host props: Get host properties structure from SDHC. This verifies that
  the API returns a valid host property structure (at a minimum, the driver
  must initialize all fields of the structure to zero.)

* Set_IO test: Verify that the SDHC will reject clock frequencies outside of
  the frequency range it claims to support via sdhc_get_host_props.

* Card presence test. Verify that the SDHC detects card presence.

* Request test: Make a request to read the card interface condition,
  and verify that valid data is returned.

Note that this test does not verify the tuning or card busy api, as the SD
specification is state based, and testing these portions of the SDHC would
require implementing a large portion of the SD subsystem in this test.