diff options
| -rw-r--r-- | Documentation/rtc.txt | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/rtc.txt b/Documentation/rtc.txt index c931d613f641..e20b19c1b60d 100644 --- a/Documentation/rtc.txt +++ b/Documentation/rtc.txt | |||
| @@ -180,9 +180,10 @@ driver returns ENOIOCTLCMD. Some common examples: | |||
| 180 | * RTC_IRQP_SET, RTC_IRQP_READ: the irq_set_freq function will be called | 180 | * RTC_IRQP_SET, RTC_IRQP_READ: the irq_set_freq function will be called |
| 181 | to set the frequency while the framework will handle the read for you | 181 | to set the frequency while the framework will handle the read for you |
| 182 | since the frequency is stored in the irq_freq member of the rtc_device | 182 | since the frequency is stored in the irq_freq member of the rtc_device |
| 183 | structure. Also make sure you set the max_user_freq member in your | 183 | structure. Your driver needs to initialize the irq_freq member during |
| 184 | initialization routines so the framework can sanity check the user | 184 | init. Make sure you check the requested frequency is in range of your |
| 185 | input for you. | 185 | hardware in the irq_set_freq function. If you cannot actually change |
| 186 | the frequency, just return -ENOTTY. | ||
| 186 | 187 | ||
| 187 | If all else fails, check out the rtc-test.c driver! | 188 | If all else fails, check out the rtc-test.c driver! |
| 188 | 189 | ||