Title: [3979] trunk/drivers/rtc/rtc-bfin.c: if we dont define irq_set_freq, the common rtc-dev layer will give us the same behavior of returning ENOTTY
Revision
3979
Author
vapier
Date
2007-12-04 09:20:38 -0600 (Tue, 04 Dec 2007)

Log Message

if we dont define irq_set_freq, the common rtc-dev layer will give us the same behavior of returning ENOTTY

Diffstat

 rtc-bfin.c |   15 ---------------
 1 files changed, 15 deletions(-)

Modified Paths

Diff

Modified: trunk/drivers/rtc/rtc-bfin.c (3978 => 3979)


--- trunk/drivers/rtc/rtc-bfin.c	2007-12-04 11:16:35 UTC (rev 3978)
+++ trunk/drivers/rtc/rtc-bfin.c	2007-12-04 15:20:38 UTC (rev 3979)
@@ -381,20 +381,6 @@
 #undef yesno
 }
 
-/**
- *	bfin_irq_set_freq - make sure hardware supports requested freq
- *	@dev: pointer to RTC device structure
- *	@freq: requested frequency rate
- *
- *	The Blackfin RTC can only generate periodic events at 1 per
- *	second (1 Hz), so reject any attempt at changing it.
- */
-static int bfin_irq_set_freq(struct device *dev, int freq)
-{
-	dev_dbg_stamp(dev);
-	return -ENOTTY;
-}
-
 static struct rtc_class_ops bfin_rtc_ops = {
 	.open          = bfin_rtc_open,
 	.release       = bfin_rtc_release,
@@ -404,7 +390,6 @@
 	.read_alarm    = bfin_rtc_read_alarm,
 	.set_alarm     = bfin_rtc_set_alarm,
 	.proc          = bfin_rtc_proc,
-	.irq_set_freq  = bfin_irq_set_freq,
 };
 
 static int __devinit bfin_rtc_probe(struct platform_device *pdev)
_______________________________________________
Linux-kernel-commits mailing list
[email protected]
http://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits

Reply via email to