On 29/03/2017 15:22, Alexander Kochetkov wrote:
> Hello, Daniel.
Hi Alexander,
> Due to recent comments from Mark[1], may be is better to apply v6[2] series
> instead of v7[3]?
> Because my main goal was to fix wall time on rk3188. And I did it the same
> way how that was
> already done for
On 29/03/2017 15:22, Alexander Kochetkov wrote:
> Hello, Daniel.
Hi Alexander,
> Due to recent comments from Mark[1], may be is better to apply v6[2] series
> instead of v7[3]?
> Because my main goal was to fix wall time on rk3188. And I did it the same
> way how that was
> already done for
Hello, Daniel.
Due to recent comments from Mark[1], may be is better to apply v6[2] series
instead of v7[3]?
Because my main goal was to fix wall time on rk3188. And I did it the same way
how that was
already done for other timer drivers (one of possible solution).
You can rename
Hello, Daniel.
Due to recent comments from Mark[1], may be is better to apply v6[2] series
instead of v7[3]?
Because my main goal was to fix wall time on rk3188. And I did it the same way
how that was
already done for other timer drivers (one of possible solution).
You can rename
Hello, Daniel, Heiko.
Here is try 7 :) Could you please take a look into it?
rockchip_timer init code implemented using CLOCKEVENT_OF_DECLARE()
introduced in commit 0c8893c9095d ("clockevents: Add a clkevt-of
mechanism like clksrc-of")
There is change in the arch/arm/mach-rockchip/rockchip.c.
Hello, Daniel, Heiko.
Here is try 7 :) Could you please take a look into it?
rockchip_timer init code implemented using CLOCKEVENT_OF_DECLARE()
introduced in commit 0c8893c9095d ("clockevents: Add a clkevt-of
mechanism like clksrc-of")
There is change in the arch/arm/mach-rockchip/rockchip.c.
6 matches
Mail list logo
