drivers/virtio/virtio_rtc_arm.c
Source file repositories/reference/linux-study-clean/drivers/virtio/virtio_rtc_arm.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/virtio/virtio_rtc_arm.c- Extension
.c- Size
- 518 bytes
- Lines
- 24
- Domain
- Driver Families
- Bucket
- drivers/virtio
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
Dependency Surface
linux/clocksource_ids.huapi/linux/virtio_rtc.hvirtio_rtc_internal.h
Detected Declarations
function Copyright
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-or-later
/*
* Provides cross-timestamp params for Arm.
*
* Copyright (C) 2022-2023 OpenSynergy GmbH
* Copyright (c) 2024 Qualcomm Innovation Center, Inc. All rights reserved.
*/
#include <linux/clocksource_ids.h>
#include <uapi/linux/virtio_rtc.h>
#include "virtio_rtc_internal.h"
/* see header for doc */
int viortc_hw_xtstamp_params(u8 *hw_counter, enum clocksource_ids *cs_id)
{
*hw_counter = VIRTIO_RTC_COUNTER_ARM_VCT;
*cs_id = CSID_ARM_ARCH_COUNTER;
return 0;
}
Annotation
- Immediate include surface: `linux/clocksource_ids.h`, `uapi/linux/virtio_rtc.h`, `virtio_rtc_internal.h`.
- Detected declarations: `function Copyright`.
- Atlas domain: Driver Families / drivers/virtio.
- Implementation status: source implementation candidate.
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.