From: Gregoire Gentil <gregoire@gentil.com>
To: unlisted-recipients:; (no To-header on input)
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Problem between rt-patches and OMAP SPI driver
Date: Wed, 22 Aug 2012 12:49:46 -0700 [thread overview]
Message-ID: <503537DA.4070809@gentil.com> (raw)
In-Reply-To: <10950377.h1F1h7Gs2a@dabox>
Hello,
When applying the rt patches, the OMAP SPI driver referenced below
doesn't work well. It's working well without the rt patches.
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=blob;f=drivers/spi/omap2_mcspi.c;h=969cdd2fe124602d1e65c4218190ed3e7d78ccf6;hb=02f8c6aee8df3cdc935e9bdd4f2d020306035dbe
More precisely, I'm getting a lot of "TXS timed out" and "RXS timed out"
on line 485/495.
Q1. Has anyone made work OMAP SPI driver with rt patches?
Q2. How can I debug such problem? I have converted all the spin_lock_irq
to raw_spin_lock_* without being sure if it's a good idea. But in any
case, the result is the same.
Q3. More generically, while considering a new driver, what needs to be
watched and patched from the rt point of view to play nicely with the
real-time architecture? All the mutex? Anything in the worker function?
I know that I won't become a RT expert overnight, but I'm trying to
understand.
Many thanks in advance for any help or pointer,
Grégoire
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-08-22 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 19:22 [ANNOUNCE] 3.4.9-rt17 Steven Rostedt
2012-08-22 11:48 ` Tim Sander
2012-08-22 13:08 ` Tim Sander
2012-08-24 8:32 ` Tim Sander
2012-08-22 19:49 ` Gregoire Gentil [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=503537DA.4070809@gentil.com \
--to=gregoire@gentil.com \
--cc=linux-rt-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).