From: Philippe Gerum <rpm@xenomai.org>
To: Nitin Kulkarni <nitink@kth.se>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Problem with gpio interrupts for xenomai3 on Intel joule
Date: Fri, 30 Jun 2017 21:40:01 +0200 [thread overview]
Message-ID: <d5ed27c7-6db6-823c-cd52-81b6598f0e73@xenomai.org> (raw)
In-Reply-To: <1498646840487.52373@kth.se>
On 06/28/2017 12:47 PM, Nitin Kulkarni wrote:
> Hi Philippe,
> Thanks for the review and you comments are very helpful.
> I think my fix-up would just be fine for us as we just need one gpio interrupt to process SPI transfers
> with an XMOS microcontroller.
>
> Hence my next challenge is to do SPI communication in real-time domain (My colleague
> Stefano once had a discussion over emails with you I think about streaming audio over SPI in realtime domain),
> I know that I will have to port the spi-pxa2xx platform driver to RTDM.
> i was looking at the bcm2835 spi driver that you have ported for RTDM.
> Is this a good reference to start ?
At least to understand which handler need to be provided to Cobalt's
generic SPI core, yes.
--
Philippe.
prev parent reply other threads:[~2017-06-30 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.117.1496166485.4225.xenomai@xenomai.org>
2017-05-30 18:02 ` [Xenomai] problem gpio interrupts xenomai3 on the raspberry pi 2 (or 3) Nitin Kulkarni
2017-05-31 7:16 ` Philippe Gerum
2017-05-31 10:34 ` Nitin Kulkarni
2017-06-01 7:11 ` Philippe Gerum
[not found] ` <1497222185664.65276@kth.se>
2017-06-12 11:02 ` [Xenomai] Problem with gpio interrupts for xenomai3 on Intel joule Nitin Kulkarni
2017-06-14 8:27 ` Philippe Gerum
2017-06-14 12:57 ` Nitin Kulkarni
2017-06-25 13:59 ` Philippe Gerum
2017-06-28 10:47 ` Nitin Kulkarni
2017-06-30 19:40 ` Philippe Gerum [this message]
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=d5ed27c7-6db6-823c-cd52-81b6598f0e73@xenomai.org \
--to=rpm@xenomai.org \
--cc=nitink@kth.se \
--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.