All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Nitin Kulkarni <nitink@kth.se>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] problem gpio interrupts xenomai3 on the raspberry pi 2 (or 3)
Date: Wed, 31 May 2017 09:16:58 +0200	[thread overview]
Message-ID: <e1ed397b-c902-7b7d-5d1c-e78d9c5f8bf0@xenomai.org> (raw)
In-Reply-To: <1496167354451.78382@kth.se>

On 05/30/2017 08:02 PM, Nitin Kulkarni wrote:
> Hi Philippe,
>>From your reply I guess its the same issue  with my SoC also. Do you think in my case the Intel joule pinctrl driver is not aware of Ipipe ?
> Do you have any instances where an x86 based SoC was ported to solve this issue ?
> Thanks for the info it explains a lot of things now.

What is the output of /proc/interrupts on your board?

-- 
Philippe.


  reply	other threads:[~2017-05-31  7:16 UTC|newest]

Thread overview: 14+ 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 [this message]
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
     [not found] <mailman.115.1496162312.4225.xenomai@xenomai.org>
2017-05-30 17:47 ` [Xenomai] problem gpio interrupts xenomai3 on the raspberry pi 2 (or 3) Nitin Kulkarni
2017-05-30 16:38 Harco Kuppens
2017-05-30 17:30 ` Philippe Gerum
2017-05-30 19:32   ` Harco Kuppens

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=e1ed397b-c902-7b7d-5d1c-e78d9c5f8bf0@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.