From: "Wayne Call" <wcall@domain.hid>
To: Xenomai-help@domain.hid
Subject: [Xenomai-help] RT context
Date: Fri, 28 Jan 2011 13:27:53 -0700 [thread overview]
Message-ID: <002601cbbf29$d77f4e40$867deac0$@com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
In the heartbeat example, there is the following comment:
/* Note: The I-pipe patch for blackfin ensures that
gpio_set_value
* (among other services) can safely be called from RT
context. */
So this states that the gpio_set_value can be called from an RT context.
What about an I2C driver, or an SPI driver? There are linux kernel drivers
to support these devices. Does it make sense to continue to use these
drivers in the linux kernel, and somehow have an RT context that can tap
into this data? Does an RT context take precedence over the linux kernel
I2C and SPI drivers? The Xenomai is its own kernel and somehow interacts
and works together with the linux kernel. Do I have to re-structure a linux
kernel I2C driver completely into a Xenomai I2C driver?
In the past I have written a linux kernel driver on top of the I2C driver to
collect I2C data into a buffer. I also wrote a Xenomai driver that makes
calls into this top level linux kernel I2C driver to get the data. And
there is a Xenomai user application, running an RT context, that gets the
data from the Xenomai driver.
Is there a particular strategy I should be using for the I2C and SPI
interfaces?
Wayne
[-- Attachment #2: Type: text/html, Size: 3521 bytes --]
next reply other threads:[~2011-01-28 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 20:27 Wayne Call [this message]
2011-01-28 21:19 ` [Xenomai-help] RT context Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2012-01-17 18:11 [Xenomai-help] rt context Peter Hua
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='002601cbbf29$d77f4e40$867deac0$@com' \
--to=wcall@domain.hid \
--cc=Xenomai-help@domain.hid \
/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.