From: Jim Cromie <jim.cromie@domain.hid>
To: xenomai-core <xenomai@xenomai.org>, Jan Kiszka <jan.kiszka@domain.hid>
Subject: [Xenomai-core] GPIO and RTDM
Date: Wed, 14 Jun 2006 13:37:40 -0600 [thread overview]
Message-ID: <44906584.60503@domain.hid> (raw)
hi Jan, everyone,
Ive worked up a patchset to add a GPIO driver for the chip on my mobo.
I adapted an existing one, drivers/char/scx200_gpio,
and created drivers/char/pc8736x_gpio
When doing this, I _oversimplified_ my problem by disregarding RTDM,
and Im hoping I can just _retrofit_ as needed.
the chip is on an ISA bus, a user-space C program can read the pins at
(this) rate:
Wed Jun 14 13:24:13 MDT 2006
Linux soekris 2.6.17-rc6-gpio-sk #4 Sun Jun 11 20:43:10 MDT 2006 i586
GNU/Linux
opened /dev/gpio-17, for 1 loops, 1000000 samples
read 1000000 samples in 7.8434 sec, rate: 127494.9460 samples/sec
opened /dev/led, for 1 loops, 1000000 samples
read 1000000 samples in 5.4116 sec, rate: 184788.5056 samples/sec
(obviously speed isnt latency, but theres some correlation ..)
I dont actually have a Real Question, to I'll throw out a placeholder -
What are the top 3-5 things to do or look at
in order to check the compatibility of my patches with RTDM ?
Separately..
In this GPIO work, I concluded that I needed to add a sysfs interface
to my driver, in order to better fit with LKML expectations.
What I did so far works, and seems to hang together coherently, but
insofar as it
is the 1st time (to my knowledge) that a uniform treatment has been tried,
I might have painted myself / all-of-us into a corner.
Hopefully not, but you folks have a keener perception of these things.
Ill send shortly.
tia
jimc
next reply other threads:[~2006-06-14 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 19:37 Jim Cromie [this message]
2006-06-14 19:43 ` [Xenomai-core] Re: GPIO and RTDM Jim Cromie
2006-06-15 8:10 ` Jan Kiszka
2006-06-17 19:44 ` Jim Cromie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44906584.60503@domain.hid \
--to=jim.cromie@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.