Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration
Extension: [no extension]
Size: 763 bytes
Lines: 15
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/rtc/rtc0/device/rtc_calibration
Date:           Oct 2011
KernelVersion:  3.0
Contact:        Mark Godfrey <mark.godfrey@stericsson.com>
Description:    Attribute for calibrating ST-Ericsson AB8500 Real Time Clock
		The rtc_calibration attribute allows the userspace to
                calibrate the AB8500.s 32KHz Real Time Clock.
                Every 60 seconds the AB8500 will correct the RTC's value
                by adding to it the value of this attribute.

                The range of the attribute is -127 to +127 in units of
                30.5 micro-seconds (half-parts-per-million of the 32KHz clock)
Users:          The /vendor/st-ericsson/base_utilities/core/rtc_calibration
                daemon uses this interface.

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.