Documentation/ABI/testing/sysfs-bus-optee-devices

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-bus-optee-devices

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-bus-optee-devices
Extension: [no extension]
Size: 760 bytes
Lines: 18
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
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

What:		/sys/bus/tee/devices/optee-ta-<uuid>/
Date:           May 2020
KernelVersion   5.8
Contact:        op-tee@lists.trustedfirmware.org
Description:
		OP-TEE bus provides reference to registered drivers under this directory. The <uuid>
		matches Trusted Application (TA) driver and corresponding TA in secure OS. Drivers
		are free to create needed API under optee-ta-<uuid> directory.

What:		/sys/bus/tee/devices/optee-ta-<uuid>/need_supplicant
Date:		November 2023
KernelVersion:	6.7
Contact:	op-tee@lists.trustedfirmware.org
Description:
		Allows to distinguish whether an OP-TEE based TA/device requires user-space
		tee-supplicant to function properly or not. This attribute will be present for
		devices which depend on tee-supplicant to be running.

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
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.