zephyr/tests/drivers/gpio/gpio_basic_api
Hu Zhenyu 99ab3fba54 tests: Change the result compare method in pin_get_config()
Fixes #47921
When setting a GPIO to certain value, and then get the GPIO value, on some
platforms, such as ITE, these two values may not be the same. For example
setting GPIO_OUTPUT | GPIO_OUTPUT_INT_HIGH, it will read back
GPIO_OUTPUT | GPIO_OUTPUT_INT_HIGH | GPIO_VOLTAGE_3P3. This is as expected,
as GPIO_VOLTAGE is a read only property. So when comparing the gpio set
and get values, it is necessary to filter the read only bits first and
then compare to the set value.

Signed-off-by: Hu Zhenyu <zhenyu.hu@intel.com>
2022-09-07 15:34:28 +02:00
..
boards tests: Remove label property from devicetree overlays 2022-07-28 20:52:20 +02:00
dts/bindings
src tests: Change the result compare method in pin_get_config() 2022-09-07 15:34:28 +02:00
CMakeLists.txt
prj.conf tests: drivers: gpio: move the gpio basic test to new ztest API 2022-08-29 10:31:45 +02:00
README.txt
testcase.yaml tests: drivers: gpio: gpio_basic_api: nrf: Extend test 2021-12-22 12:03:00 +01:00

GPIO 2-Pin Test
###############

This application tests the GPIO subsystem using a hardware configuration
where two GPIOs are directly wired together.  The test pins are
identified through a test-specific devicetree binding in the `dts/`
subdirectory, implemented for specific boards by overlay files in the
`boards/` directory.

For some boards `src/main.c` may also need to be extended to configure
the selected pins for use as GPIOs.

Only boards for which an overlay is present can pass this test.  Boards
without an overlay, or for which the required wiring is not provided,
will fail with an error like this:

    Validate device GPIO_0
    Check GPIO_0 output 2 connected to input 3
    FATAL output pin not wired to input pin? (out high => in low)

No special build options are required to make use of the overlay.