ulisha
> Cc: Alessandro Zummo ; Soren Brinkmann
> ; Michal Simek ; rtc-
> li...@googlegroups.com; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org; Punnaiah Choudary Kalluri ;
> Anirudha Sarangi ; Srikanth Vemula
> ; Srinivas Goud
> Subject: Re: [PATCH 3/3] RTC
On 20/04/2016 at 10:31:06 +, Anurag Kumar Vulisha wrote :
> > Yeas, I understood that. But my question was whether the interrupt handling
> > was necessary at all.
> > Instead of waiting for an interrupt to set time_updated, can't you simply
> > read
> > RTC_INT_STS and check for the RTC_INT_S
ps.com; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org; Punnaiah Choudary Kalluri ;
> Anirudha Sarangi ; Srikanth Vemula
> ; Srinivas Goud
> Subject: Re: [PATCH 3/3] RTC: Update seconds time programming logic
>
> On 20/04/2016 at 07:10:22 +, Anurag Kumar Vulish
On 20/04/2016 at 07:10:22 +, Anurag Kumar Vulisha wrote :
> The reason for me keeping this logic is, our RTC controller updates the read
> register after 1 sec
> delay, so when read , it gives 1 sec delay(correct time - 1 sec). So to avoid
> that we are programming
> load time + 1sec into the
ps.com; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org; Punnaiah Choudary Kalluri ;
> Anirudha Sarangi ; Srikanth Vemula
> ; Anurag Kumar Vulisha
> Subject: Re: [PATCH 3/3] RTC: Update seconds time programming logic
>
>
> Hi,
>
> Please use rtc: zynqmp i
Hi,
Please use rtc: zynqmp in your subject line.
On 12/04/2016 at 17:45:46 +0530, Anurag Kumar Vulisha wrote :
> @@ -78,6 +85,17 @@ static int xlnx_rtc_set_time(struct device *dev, struct
> rtc_time *tm)
>
> writel(new_time, xrtcdev->reg_base + RTC_SET_TM_WR);
>
> + /*
> + *
6 matches
Mail list logo