tools/testing/selftests/hid/run-hid-tools-tests.sh

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/hid/run-hid-tools-tests.sh

Extension

.sh

Size

758 bytes

Lines

31

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: tools

Status

atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#!/bin/sh
# SPDX-License-Identifier: GPL-2.0
# Runs tests for the HID subsystem

KSELFTEST_SKIP_TEST=4

if ! command -v python3 > /dev/null 2>&1; then
	echo "hid-tools: [SKIP] python3 not installed"
	exit $KSELFTEST_SKIP_TEST
fi

if ! python3 -c "import pytest" > /dev/null 2>&1; then
	echo "hid: [SKIP] pytest module not installed"
	exit $KSELFTEST_SKIP_TEST
fi

if ! python3 -c "import pytest_tap" > /dev/null 2>&1; then
	echo "hid: [SKIP] pytest_tap module not installed"
	exit $KSELFTEST_SKIP_TEST
fi

if ! python3 -c "import hidtools" > /dev/null 2>&1; then
	echo "hid: [SKIP] hid-tools module not installed"
	exit $KSELFTEST_SKIP_TEST
fi

TARGET=${TARGET:=.}

echo TAP version 13
python3 -u -m pytest $PYTEST_XDIST ./tests/$TARGET --tap-stream --udevd

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.