X-Git-Url: http://pilppa.org/gitweb/?a=blobdiff_plain;f=Documentation%2Frtc.txt;h=e20b19c1b60da04b95cfc62a0cec57428a53bb12;hb=152ff9be2ed11e76ed3014b94eacdd6bc9275518;hp=c931d613f6410cb7dce6732ac1f68ddaf6a3ee9d;hpb=d9ff963801e4f7648c55a27413a1b1de59480a30;p=linux-2.6-omap-h63xx.git

diff --git a/Documentation/rtc.txt b/Documentation/rtc.txt
index c931d613f64..e20b19c1b60 100644
--- a/Documentation/rtc.txt
+++ b/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!