On 02/11/2016 at 08:23:32 +0000, Meng Yi wrote :
> > +
> > +static int ftm_alarm_irq_enable(struct device *dev, unsigned int
> > +enabled) {
> > + if (enabled)
> > + ftm_irq_enable(true);
> > + else
> > + ftm_irq_enable(false);
> > +
> > + return 0;
> > +}
> > +
> > +static int nxp_ftm_rtc_read_time(struct device *dev, struct rtc_time
> > +*tm) {
> > + struct timeval time;
> > + unsigned long local_time;
> > +
> > + do_gettimeofday(&time);
> > + local_time = (u32)(time.tv_sec - (sys_tz.tz_minuteswest * 60));
> > + rtc_time_to_tm(local_time, tm);
> > +
> > + return 0;
> > +}
> > +
>
> This is not really getting time from the RTC since FTM is not a RTC device,
> But we need to get the time to setup alarm, so we are using system time for
> now.
> Anybody have better idea?
>
No, that seems fine to me. I'll review the rest of the driver.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups
"rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
