Documentation/ABI/testing/sysfs-class-rc-nuvoton

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-class-rc-nuvoton

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-class-rc-nuvoton
Extension: [no extension]
Size: 594 bytes
Lines: 16
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/class/rc/rc<N>/wakeup_data
Date:		Mar 2016
KernelVersion:	4.6
Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Description:
		Reading this file returns the stored CIR wakeup sequence.
		It starts with a pulse, followed by a space, pulse etc.
		All values are in microseconds.
		The same format can be used to store a wakeup sequence
		in the Nuvoton chip by writing to this file.

		Note: Some systems reset the stored wakeup sequence to a
		factory default on each boot. On such systems store the
		wakeup sequence in a file and set it on boot using e.g.
		a udev rule.

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.