From a4b79be80720a4cfc73862886b1c63f410268611 Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Wed, 14 Nov 2007 16:58:43 -0800 Subject: [PATCH] --- yaml --- r: 73668 b: refs/heads/master c: 108b4c3638be251d6b42eaa633e8a6b852b960f0 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/rtc.txt | 7 ++++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index 668f94f80af2..baf3679dd0dd 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: fcbaa088fc8625381bd1096bc2eedc4f58a1572c +refs/heads/master: 108b4c3638be251d6b42eaa633e8a6b852b960f0 diff --git a/trunk/Documentation/rtc.txt b/trunk/Documentation/rtc.txt index c931d613f641..e20b19c1b60d 100644 --- a/trunk/Documentation/rtc.txt +++ b/trunk/Documentation/rtc.txt @@ -180,9 +180,10 @@ driver returns ENOIOCTLCMD. Some common examples: * RTC_IRQP_SET, RTC_IRQP_READ: the irq_set_freq function will be called to set the frequency while the framework will handle the read for you since the frequency is stored in the irq_freq member of the rtc_device - structure. Also make sure you set the max_user_freq member in your - initialization routines so the framework can sanity check the user - input for you. + structure. Your driver needs to initialize the irq_freq member during + init. Make sure you check the requested frequency is in range of your + hardware in the irq_set_freq function. If you cannot actually change + the frequency, just return -ENOTTY. If all else fails, check out the rtc-test.c driver!