Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1677657 > unrolled thread

Best practise for a polling device driver ?

Started by"Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
First post2017-06-29 14:10 +0200
Last post2017-06-29 14:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel


Contents

  Best practise for a polling device driver ? "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net> - 2017-06-29 14:10 +0200

#1677657 — Best practise for a polling device driver ?

From"Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
Date2017-06-29 14:10 +0200
SubjectBest practise for a polling device driver ?
Message-ID<tXGqK-7pH-13@gated-at.bofh.it>
Hi folks,

I'm currently writing a driver for an (pseudo-)serial device
(actually, a bunch of HW fifo's, which look like serial controllers
to the host), which only supports polling, no interrupts.

So far, I'm just using a kthread in a loop, but that would have to
run w/ high priority sleep very short (needs to transfer several
MB/s on a am33xx), so probably not a good idea.

Another option could be using timers for just looking at the status
registers and issue sw interrupts, which are then handled just like
the w/ the usual interrupt-driven serial ports (IOW: mimic an
interrupt controller).

What do you folks thinkt about that ?


thx.
--mtx

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web