All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jeremy Brown <jhbrown@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] kernel warnings and oopses calling gpiolib functions from xenomai kernel space
Date: Sat, 03 Jul 2010 19:20:28 +0200	[thread overview]
Message-ID: <4C2F715C.9050800@domain.hid> (raw)
In-Reply-To: <4C2F24CF.7090309@domain.hid>

Gilles Chanteperdrix wrote:
> Jeremy Brown wrote:
>> Thanks in advance for any and all help!
> 
> Hi,
> 
> from your post, we can conclude that gpio_set_value is a Linux kernel
> function which can yet not be used in Xenomai context (you could
> probably even get more explicit messages by enabling I-pipe debugging).
> I am going to try and propose a fix for this issue, will send you a
> patch ASAP.
> 
> Note that the issue is more an Adeos I-pipe issue than a Xenomai issue,
> so I am more interested in knowing what version of adeos than what
> version of Xenomai you are using. But chances that the problem exists
> with all versions anyway.

Could you try the following patch?

diff --git a/arch/arm/plat-omap/gpio.c b/arch/arm/plat-omap/gpio.c
index 589a4bb..f1d85ff 100644
--- a/arch/arm/plat-omap/gpio.c
+++ b/arch/arm/plat-omap/gpio.c
@@ -195,7 +195,7 @@ struct gpio_bank {
 #endif
 	u32 level_mask;
 	u32 toggle_mask;
-	spinlock_t lock;
+	ipipe_spinlock_t lock;
 	struct gpio_chip chip;
 	struct clk *dbck;
 	u32 mod_usage;

-- 
					    Gilles.


  reply	other threads:[~2010-07-03 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 20:20 [Xenomai-help] kernel warnings and oopses calling gpiolib functions from xenomai kernel space Jeremy Brown
2010-07-03 11:53 ` Gilles Chanteperdrix
2010-07-03 17:20   ` Gilles Chanteperdrix [this message]
2010-07-04  6:09     ` Jeremy Brown
2010-07-06 17:03     ` Jeremy Brown

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=4C2F715C.9050800@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jhbrown@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.