On Thu, Jun 22, 2017 at 12:24 PM, Matthias Brugger
Hi Roger,
On 22/06/17 10:38, Roger Oberholtzer wrote:
I am looking at making a custom Raspberry PI3 kernel module that needs to deal with the various I/O pins. I need a driver because the activity is quite high. So a python or other high-level interface will not be possible. It will most likely do the majority of work in the driver's interrupt routine that, I hope, can be called when a pin or pins change state.
My questions are: 1. Has anyone experienced any difficulties with making custom drivers on openSUSE running on the Pi3? 2. Are there any drivers that are being loaded by openSUSE that fiddle with the I/O lines that I may need to disable? Currently, nothing is connected to the I/O lines.
Which pins are we talking about?
That's flexible. We can connect to any pins that are best suited.
Which interface do you want to use (SPI, I2C etc)?
It is not a standard interface. Just a trigger pin. But it can trigger up to 32 kHz. And we need to react to each of them. We would like to try to stay away from commonly used lines so we could possibly also attach a device that uses such a protocol. But that is a secondary concern.
Which sensor do you want to connect?
It is a device that provides pulses related to movement. We monitor these and take action on them. Some actions are the manipulation of other lines. Some are information packets (UDP) to interested clients (at a much reduced rate).
Which version of openSUSE do you use?
Tumbleweed. That is flexible. We use Tumbleweed because that is the one that installed. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org