All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Gautier HAOUY <gautier.haouy@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] imx28 linux 3.10.32 + ipipe v7 + GPIO IRQ machine freeze
Date: Thu, 29 Jan 2015 12:02:53 +0100	[thread overview]
Message-ID: <20150129110253.GB2698@hermes.click-hack.org> (raw)
In-Reply-To: <20150129104650.GA2698@hermes.click-hack.org>

On Thu, Jan 29, 2015 at 11:46:50AM +0100, Gilles Chanteperdrix wrote:
> On Thu, Jan 29, 2015 at 09:46:13AM +0100, Gautier HAOUY wrote:
> > Hello everyone,
> > 
> > I am kindly requesting your help today as I am facing a complete freeze on
> > an Freescale iMX28 based board (armadeus APF28-Dev).
> > I have developed a very simple kernel module which registers a GPIO
> > interrupt handler, working properly on linux 3.10.32 kernel.
> > The same code, compiled on a 3.10.32 + ipipe7 (also tested on ipipe v4)
> > patched kernel generates a machine freeze on IRQ reception, without message
> > and any other possibility than resetting the board.
> > 
> > I would appreciate any help/hint/procedure I could use to dive into the
> > problem and solve it.
> > Hoping to help others afterwards,
> > Best regards,
> > G0TieR.
> 
> What is the problem exactly. Only applying the I-pipe patch breaks
> the GPIOs, or you need to compile the kernel with CONFIG_IPIPE?

I assume the latter. Please replace the calls to generic_handle_irq
with ipipe_handle_demuxed_irq in drivers/gpio/gpio-mxs.c. The change
got forgotten when the gpio file moved to drivers/gpio it seems.

-- 
					    Gilles.


  reply	other threads:[~2015-01-29 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29  8:46 [Xenomai] imx28 linux 3.10.32 + ipipe v7 + GPIO IRQ machine freeze Gautier HAOUY
2015-01-29 10:46 ` Gilles Chanteperdrix
2015-01-29 11:02   ` Gilles Chanteperdrix [this message]
2015-01-29 11:45     ` Gautier HAOUY
2015-01-29 11:14 ` Kevin Kasal

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=20150129110253.GB2698@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=gautier.haouy@gmail.com \
    --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.