On Mon, Jan 30, 2017 at 02:04:42PM +0300, Alexander Kochetkov wrote:
>
> > 25 янв. 2017 г., в 15:21, Daniel Lezcano
> > написал(а):
> >
> > Hopefully, that can help to do some housework in the directory, perhaps
> > split the drivers in to entities, for example:
> >
On Mon, Jan 30, 2017 at 02:04:42PM +0300, Alexander Kochetkov wrote:
>
> > 25 янв. 2017 г., в 15:21, Daniel Lezcano
> > написал(а):
> >
> > Hopefully, that can help to do some housework in the directory, perhaps
> > split the drivers in to entities, for example:
> > - clksrc-rockchip.c
> >
> 25 янв. 2017 г., в 15:21, Daniel Lezcano
> написал(а):
>
> Hopefully, that can help to do some housework in the directory, perhaps
> split the drivers in to entities, for example:
> - clksrc-rockchip.c
> - clkevt-rockchip.c
>
> Also, it gives the
> 25 янв. 2017 г., в 15:21, Daniel Lezcano
> написал(а):
>
> Hopefully, that can help to do some housework in the directory, perhaps
> split the drivers in to entities, for example:
> - clksrc-rockchip.c
> - clkevt-rockchip.c
>
> Also, it gives the possibility to declare
The current code uses the CLOCKSOURCE_OF_DECLARE macro to fill the clksrc
table with a t-uple (name, init_function).
Unfortunately it ends up to the clockevent and the clocksource being
both initialized with this macro. It is not a problem by itself but there
is not a clear distinction between a
The current code uses the CLOCKSOURCE_OF_DECLARE macro to fill the clksrc
table with a t-uple (name, init_function).
Unfortunately it ends up to the clockevent and the clocksource being
both initialized with this macro. It is not a problem by itself but there
is not a clear distinction between a
6 matches
Mail list logo