On Tuesday, June 16, 2015 at 3:59:34 AM UTC+3, Krzysztof Kozłowski wrote:

2015-06-16 3:26 GMT+09:00 Alexey Mednyy <swe...@gmail.com <javascript:>>: 

quoted

Hello all! 

I'm trying to add wakealarm support to rtc-mc13xxx driver. But I've 

faced some troubles. 

quoted

It's using nested IRQs over mc13xxx-core driver. 
What I've done: 
1. Added device_init_wakeup to both mc13xxx-core (parent irq) and to 

rtc-mc13xxx 

quoted

2. Added dev_pm_ops to both core and rtc 
3. Added enable_irq_wake to core suspend for core irq 

Consider adding it also in RTC driver. 

I tried, no luck.
 

quoted

4. Disabled 1HZ irq in rtc-mc13xxx ( do not wakeup after 1 second) 

Now I've got wakealarm file and I can write to it. But device doesn't 

wakeup. 

Does the wakealarm work fine without suspend? You can easily test it 
with rtcwake. 

Yes it works like that:
rtcwake -v -d /dev/rtc0 -s 5 -m on

But not working with real suspend to mem.

For some reason irq become masked while suspending, as I mentioned in 
before:

I've added some printk's to suspend core suspend (as it goes after child 

suspend) and I can see that IRQ_TODA bit of IRQ_MASK1 register in mc13xxx 
is masked(turned off).
For some reason rtc or regmap irq, disabled TODA irq before suspend.
Can't figure why. 

 
So questions still the same:

1. Why TODA irq turned off before suspend?
2. Is there any restrictions in IRQs, rtc can use for wakeup? Could it be 
regmap_irq_chips irq?

-- 
-- 
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 rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.