All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nitin Kulkarni <nitink@kth.se>
To: Philippe Gerum <rpm@xenomai.org>,
	"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 10:34:56 +0000	[thread overview]
Message-ID: <1496226896420.15161@kth.se> (raw)
In-Reply-To: <e1ed397b-c902-7b7d-5d1c-e78d9c5f8bf0@xenomai.org>

This is the output from /proc/interrupts  (Note: irq 300 is the one I have requested ) 

 root@intel-corei7-64:~# cat /proc/interrupts
            CPU0       CPU1       CPU2       CPU3
   0:         84          0          0          0   IO-APIC    2-edge      timer
   3:       7666          0          0          0   IO-APIC    3-fasteoi   mmc0
   4:          0          0          0          0   IO-APIC    4-fasteoi   idma64.7
   5:          0          0          0          0   IO-APIC    5-fasteoi   idma64.8
   6:       1276          0          0          0   IO-APIC    6-fasteoi   serial
   8:          1          0          0          0   IO-APIC    8-fasteoi   rtc0
   9:         39          0          0          0   IO-APIC    9-fasteoi   acpi
  14:          0          0          0          0   IO-APIC   14-fasteoi   INT34D1:00, INT34D1:01, INT34D1:02, INT34D1:03, INT34D1:04
  27:         70          0          0          0   IO-APIC   27-fasteoi   idma64.0, i2c_designware.0
  28:          0          0          0          0   IO-APIC   28-fasteoi   idma64.1, i2c_designware.1
  29:          0          0          0          0   IO-APIC   29-fasteoi   idma64.2, i2c_designware.2
  30:          0          0          0          0   IO-APIC   30-fasteoi   idma64.3, i2c_designware.3
  31:          0          0          0          0   IO-APIC   31-fasteoi   idma64.4, i2c_designware.4
  33:          0          0          0          0   IO-APIC   33-fasteoi   idma64.5, i2c_designware.5
  34:          0          0          0          0   IO-APIC   34-fasteoi   idma64.6, i2c_designware.6
  35:          0          0          0          0   IO-APIC   35-fasteoi   idma64.11, pxa2xx-spi.11
  36:          0          0          0          0   IO-APIC   36-fasteoi   idma64.12, pxa2xx-spi.12
  37:          0          0          0          0   IO-APIC   37-fasteoi   idma64.13, pxa2xx-spi.13
  39:       1483          0          0          0   IO-APIC   39-fasteoi   mmc1
  40:       1141          0          0          0   IO-APIC   40-fasteoi   intel_pmc_ipc
  41:          1          0          0          0   IO-APIC   41-fasteoi   bxtwc_irq_chip, bxtwc_irq_chip_level2, bxtwc_irq_chip_tmu
 120:          1          0          0          0   PCI-MSI 327680-edge      PCIe PME
 121:       4838          0          0          0   PCI-MSI 344064-edge      xhci_hcd
 122:         31          0          0          0   PCI-MSI 245760-edge      mei_me
 142:          0          0          0          0  intel-gpio   19  bq25890_irq
 300:          0          0          0          0  intel-gpio   22  test_interrupt
 371:         31          0          0          0   PCI-MSI 32768-edge      i915
 372:       1525          0          0          0   PCI-MSI 524288-edge      iwlwifi
 373:          0          0          0          0  bxtwc_irq_chip_level2    0  pmic_thermal
 374:          0          0          0          0  bxtwc_irq_chip_level2    1  pmic_thermal
 375:          0          0          0          0  bxtwc_irq_chip_level2    2  pmic_thermal
 383:          1          0          0          0  Whiskey Cove    7  ACPI:Event
 470:          1          0          0          0  bxtwc_irq_chip_level2    7  bxt_wcove_gpio
 471:          1          0          0          0  bxtwc_irq_chip_level2    5  wcove_typec
 472:          0          0          0          0  bxtwc_irq_chip_tmu   10  bxt_wcove_tmu
 473:         69          0          0          0   PCI-MSI 229376-edge      snd_hda_intel
 NMI:          0          0          0          0   Non-maskable interrupts
 LOC:      12420       8239       7278       6081   Local timer interrupts
 SPU:          0          0          0          0   Spurious interrupts
 PMI:          0          0          0          0   Performance monitoring interrupts
 IWI:          0          0          0          0   IRQ work interrupts
 RTR:          0          0          0          0   APIC ICR read retries
 RES:        600        558        934        711   Rescheduling interrupts
 CAL:        142        339        343        348   Function call interrupts
 TLB:         63         50         75         71   TLB shootdowns
 TRM:          0          0          0          0   Thermal event interrupts
 THR:          0          0          0          0   Threshold APIC interrupts
 DFR:          0          0          0          0   Deferred Error APIC interrupts
 MCE:          0          0          0          0   Machine check exceptions
 MCP:          6          6          6          6   Machine check polls
 ERR:          0
 MIS:          2
 PIN:          0          0          0          0   Posted-interrupt notification event
 PIW:          0          0          0          0   Posted-interrupt wakeup event


________________________________________
From: Philippe Gerum <rpm@xenomai.org>
Sent: Wednesday, May 31, 2017 9:16 AM
To: Nitin Kulkarni; xenomai@xenomai.org
Subject: Re: [Xenomai] problem gpio interrupts xenomai3 on the raspberry pi 2 (or 3)

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 10:34 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
2017-05-31 10:34     ` Nitin Kulkarni [this message]
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=1496226896420.15161@kth.se \
    --to=nitink@kth.se \
    --cc=rpm@xenomai.org \
    --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.