Thread (8 messages) 8 messages, 3 authors, 2018-01-20

Re: [PATCH v6 2/3] clocksource/drivers/atcpit100: VDSO support

From: Arnd Bergmann <arnd@arndb.de>
Date: 2018-01-18 11:08:17
Also in: linux-arch, linux-serial, lkml, netdev

On Mon, Jan 15, 2018 at 6:57 AM, Greentime Hu [off-list ref] wrote:
From: Rick Chen <redacted>

VDSO needs real-time cycle count to ensure the time accuracy.
Unlike others, nds32 architecture does not define clock source,
hence VDSO needs atcpit100 offering real-time cycle count
to derive the correct time.

Signed-off-by: Vincent Chen <redacted>
Signed-off-by: Rick Chen <redacted>
Signed-off-by: Greentime Hu <redacted>
I'm a bit puzzled by this patch, can you explain how the vdso actually
manages to access the clock hardware? It looks like you make the
physical address and the register offset available to user space, but
how does it end up accessing it?

      Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help