On Mon, Jan 30, 2017 at 04:13:07PM +0300, Alexander Kochetkov wrote:
>
> > 30 янв. 2017 г., в 15:04, Daniel Lezcano
> > написал(а):
> >
> > There is no case when the rockchip timer is used for the clockevent.
> The is already timer entry for rk3228 in the DT. And it act as clockevent. I
> gues
> 30 янв. 2017 г., в 15:04, Daniel Lezcano
> написал(а):
>
> There is no case when the rockchip timer is used for the clockevent.
The is already timer entry for rk3228 in the DT. And it act as clockevent. I
guess it work as backup,
but I cannot test it also. In order to not break DT compatibil
On Mon, Jan 30, 2017 at 02:20:13PM +0300, Alexander Kochetkov wrote:
>
> > 30 янв. 2017 г., в 14:04, Daniel Lezcano
> > написал(а):
> >
> > t is up to the RTC to wake up the system from suspend and there is no
> > idle state stopping the local timers on these SoCs. So, the rockchip timers
> > w
> 30 янв. 2017 г., в 14:04, Daniel Lezcano
> написал(а):
>
> t is up to the RTC to wake up the system from suspend and there is no
> idle state stopping the local timers on these SoCs. So, the rockchip timers
> won't be ever used on the rk3188, right ?
No rockchip timers where used on rk3188 b
On Tue, Jan 24, 2017 at 03:16:38PM +0300, Alexander Kochetkov wrote:
> The patch add two timers to all rk3188 based boards.
>
> The first timer is from alive subsystem and it act as a backup
> for the local timers at sleep time. It act the same as other
> SoC rockchip timers already present in ker
The patch add two timers to all rk3188 based boards.
The first timer is from alive subsystem and it act as a backup
for the local timers at sleep time. It act the same as other
SoC rockchip timers already present in kernel.
The second timer is from CPU subsystem and act as replacement
for the arm
6 matches
Mail list logo
