linux-kernel - Re: [PATCH] clockevents: Add a clkevt-of mechanism like clksrc-of

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 30 Jan 2017 14:04:42 +0300
From:   Alexander Kochetkov <al.kochet@...il.com>
To:     Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:     tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clockevents: Add a clkevt-of mechanism like clksrc-of

> 25 янв. 2017 г., в 15:21, Daniel Lezcano <daniel.lezcano@...aro.org> написал(а):
> 
> 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 clocksources separately in the
> DT and then use a clocksource from IP block while while clockevents are
> used from another IP block.

Hello, Daniel!

There is no way to do declare clocksources and clockevents in the DT now.
As I understood, it is incorrect to add properties like ‘clocksource’ or ‘clockevent’
to timer entries because this sounds like linux specific configuration. While
device tree must contain only hardware description. Thus many timer
drivers has implicit assumption: first DT timer became clocksource, second
clockevent.

If we can find the way to describe timer role in the DT, than many timer drivers
could be rewritten such a way.

Also, there is timers what use single IP to provide clocksource and clockevent
at the same time. So splitting them into two files result into more complex code.

Regards,
Alexander.