u-boot.git/test/py/tests/test_gpio.py, branch master

test/py: gpio: allow omitting gpio_op_pin

2026-03-25T20:38:15+00:00

Modify tests that make use of gpio_op_pin from env__gpio_dev_config to
be skipped if gpio_op_pin is not provided. This is useful in cases where
one might not be sure which GPIOs are safe to use as outputs that can be
toggled without causing problems.

Signed-off-by: David Lechner

test/py: gpio: removing trailing semicolons

2026-03-25T20:38:15+00:00

Remove trailing semicolons in test_gpio.py. Python does not require
them and they are considered improper style.

Signed-off-by: David Lechner

test/py: gpio: remove unused imports

2026-03-25T20:38:15+00:00

Remove unused imports in test_gpio.py.

Signed-off-by: David Lechner

test/py: Drop u_boot_ prefix on test files

2025-03-15T11:02:04+00:00

We know this is U-Boot so the prefix serves no purpose other than to
make things longer and harder to read. Drop it and rename the files.

Signed-off-by: Simon Glass 
Reviewed-by: Mattijs Korpershoek  # test_android / test_dfu

test/py: Shorten u_boot_console

2025-03-15T10:38:38+00:00

This fixture name is quite long and results in lots of verbose code.
We know this is U-Boot so the 'u_boot_' part is not necessary.

But it is also a bit of a misnomer, since it provides access to all the
information available to tests. It is not just the console.

It would be too confusing to use con as it would be confused with
config and it is probably too short.

So shorten it to 'ubman'.

Signed-off-by: Simon Glass 
Link: https://lore.kernel.org/u-boot/CAFLszTgPa4aT_J9h9pqeTtLCVn4x2JvLWRcWRD8NaN3uoSAtyA@mail.gmail.com/

test/py: gpio: Add gpio pins generic test

2024-01-29T15:31:24+00:00

Add gpio pins generic test for the set of gpio pin list to test various
gpio related functionality, such as the input, set, clear, and toggle,
it also tests the input and output functionality for shorted gpio pins.
This test depends on boardenv* configuration to define gpio pins names.

Signed-off-by: Love Kumar

test: Make test_gpio_read() independent

2022-09-12T22:06:36+00:00

This assumes that the GPIO starts as 0 but it does not if
test_gpio_input() ran first and test_gpio_exit_statuses() was skipped.
This can happen when running tests in parallel.

Fix it.

Signed-off-by: Simon Glass

cmd: gpio: Add `gpio read` subcommand

2022-04-20T15:14:39+00:00

As explained in commit 4af2a33ee5b9 ("cmd: gpio: Make `gpio input`
return pin value again") the `gpio input` is used in scripts to obtain
the value of a pin, despite the fact that CMD_RET_FAILURE is
indistinguishable from a valid pin value.
To be able to detect failures and properly use the value of a GPIO in
scripts we introduce the `gpio read` command that sets the variable
`name` to the value of the pin. Return code of the `gpio read` command
can be used to check for CMD_RET_SUCCESS or CMD_RET_FAILURE.
CONFIG_CMD_GPIO_READ is used to enable the `gpio read` command.

Signed-off-by: Diego Rondini

test/py:Update python tests for ‘gpio’ cmd

2022-04-08T19:17:23+00:00

Generic Python Test cases are developed to verfiy 'gpio' command.

Signed-off-by: Adarsh Babu Kalepalli

cmd: gpio: Make `gpio input` return pin value again

2020-03-13T13:30:30+00:00

4dbc107f4683 ("cmd: gpio: Correct do_gpio() return value") correctly
changed the behaviour of the gpio command to return CMD_RET_SUCCESS or
CMD_RET_FAILURE, but any existing script which expects the return value
to be the pin value is broken by this change.

Reinstate the legacy behaviour for `gpio input` only.

Fixes: 4dbc107f4683 ("cmd: gpio: Correct do_gpio() return value")
Signed-off-by: Alex Kiernan 
Signed-off-by: Alex Kiernan 
Reviewed-by: Simon Glass