diff options
| author | Mark Brown <broonie@kernel.org> | 2026-10-04 21:54:06 +0200 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-10-04 21:54:06 +0200 |
| commit | 9b3af3c57aeebbfe2c5a4753842ea0041f8eab2e (patch) | |
| tree | 7ca7c59e1fe4a59a9c447c6adb505d12dd714773 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 717e45f97246d1070cdf86ccd7a0fb872b45933a (diff) | |
| parent | bb5805a74e7514d39b956adcc5b24ba3bfd8b988 (diff) | |
spi: qcom-geni: Use GPIO to notify master of SPI target activity
Praveen Talari <praveen.talari@oss.qualcomm.com> says:
When operating in SPI target mode, the GENI controller relies on an
external GPIO to notify the SPI master about the target's active state.
Add support for an optional device GPIO that is asserted when a target
transfer begins and deasserted when the transfer completes, is aborted,
or hits a timeout. This allows the target to explicitly signal its
availability to the master and ensures the GPIO is released in all error
and completion paths, preventing the master from observing a stale or
incorrect target ready indication.
The ready GPIO is intentionally made optional and is requested only
when target mode is enabled. This preserves existing behaviour for
systems that do not require the signal and avoids regressions on
deployed platforms where the GPIO is already controlled from userspace.
Targets without a ready GPIO continue to operate unchanged by using
devm_gpiod_get_optional().
Link: https://patch.msgid.link/20260927-use_gpio_to_notify_master_of_spi_target_activity-v5-0-9b973623080f@oss.qualcomm.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions