linux-kernel - Best practise for a polling device driver ?

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>] [day] [month] [year] [list]

Message-ID: <ac00e8ed-b11a-faac-d8f9-1e7616e40070@gr13.net>
Date:   Thu, 29 Jun 2017 12:04:14 +0000
From:   "Enrico Weigelt, metux IT consult" <enrico.weigelt@...3.net>
To:     linux-kernel@...r.kernel.org
Subject: Best practise for a polling device driver ?

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