drivers/rtc/test_rtc_lib.c
Source file repositories/reference/linux-study-clean/drivers/rtc/test_rtc_lib.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/rtc/test_rtc_lib.c- Extension
.c- Size
- 2683 bytes
- Lines
- 107
- Domain
- Driver Families
- Bucket
- drivers/rtc
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
kunit/test.hlinux/rtc.h
Detected Declarations
function advance_datefunction rtc_time64_to_tm_test_date_rangefunction rtc_time64_to_tm_test_date_range_160000function rtc_time64_to_tm_test_date_range_1000
Annotated Snippet
// SPDX-License-Identifier: LGPL-2.1+
#include <kunit/test.h>
#include <linux/rtc.h>
/*
* Advance a date by one day.
*/
static void advance_date(int *year, int *month, int *mday, int *yday, int *wday)
{
*wday = (*wday + 1) % 7;
if (*mday != rtc_month_days(*month - 1, *year)) {
++*mday;
++*yday;
return;
}
*mday = 1;
if (*month != 12) {
++*month;
++*yday;
return;
}
*month = 1;
*yday = 1;
++*year;
}
/*
* Check every day in specified number of years interval starting on 1970-01-01
* against the expected result.
*/
static void rtc_time64_to_tm_test_date_range(struct kunit *test, int years)
{
/*
* years = (years / 400) * 400 years
* = (years / 400) * 146097 days
* = (years / 400) * 146097 * 86400 seconds
*/
time64_t total_secs = ((time64_t)years) / 400 * 146097 * 86400;
int year = 1900;
int month = 1;
int mday = 1;
int yday = 1;
int wday = 1; /* Jan 1st 1900 was a Monday */
struct rtc_time result;
time64_t secs;
const time64_t sec_offset = RTC_TIMESTAMP_BEGIN_1900 + ((1 * 60) + 2) * 60 + 3;
for (secs = 0; secs <= total_secs; secs += 86400) {
rtc_time64_to_tm(secs + sec_offset, &result);
#define FAIL_MSG "%d/%02d/%02d (%2d, %d) : %lld", \
year, month, mday, yday, wday, secs + sec_offset
KUNIT_ASSERT_EQ_MSG(test, year - 1900, result.tm_year, FAIL_MSG);
KUNIT_ASSERT_EQ_MSG(test, month - 1, result.tm_mon, FAIL_MSG);
KUNIT_ASSERT_EQ_MSG(test, mday, result.tm_mday, FAIL_MSG);
KUNIT_ASSERT_EQ_MSG(test, yday, result.tm_yday, FAIL_MSG);
KUNIT_ASSERT_EQ_MSG(test, 1, result.tm_hour, FAIL_MSG);
KUNIT_ASSERT_EQ_MSG(test, 2, result.tm_min, FAIL_MSG);
KUNIT_ASSERT_EQ_MSG(test, 3, result.tm_sec, FAIL_MSG);
KUNIT_ASSERT_EQ_MSG(test, wday, result.tm_wday, FAIL_MSG);
advance_date(&year, &month, &mday, &yday, &wday);
}
}
/*
* Checks every day in a 160000 years interval starting on 1900-01-01
* against the expected result.
*/
static void rtc_time64_to_tm_test_date_range_160000(struct kunit *test)
{
rtc_time64_to_tm_test_date_range(test, 160000);
}
/*
* Checks every day in a 1000 years interval starting on 1900-01-01
* against the expected result.
*/
static void rtc_time64_to_tm_test_date_range_1000(struct kunit *test)
{
rtc_time64_to_tm_test_date_range(test, 1000);
}
Annotation
- Immediate include surface: `kunit/test.h`, `linux/rtc.h`.
- Detected declarations: `function advance_date`, `function rtc_time64_to_tm_test_date_range`, `function rtc_time64_to_tm_test_date_range_160000`, `function rtc_time64_to_tm_test_date_range_1000`.
- Atlas domain: Driver Families / drivers/rtc.
- 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.