Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: TI-Davinci 6446 oops on interrupts
Date: Mon, 6 Jun 2011 16:54:25 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1106061650210.13964@ionos> (raw)
In-Reply-To: <4DECD8C0.6010908@freyther.de>

On Mon, 6 Jun 2011, Holger Hans Peter Freyther wrote:

> On 06/06/2011 02:41 PM, Holger Freyther wrote:
> > Hi,
> > 
> > my not mainlined with custom drivers board support seems to suffer from an
> > issue introduced by moving the irq.c to the generic GPIO interrupt code
> > (aac4dd1dab8acfc244d697473d2a5f4424a5746c, reverting it makes the oops go
> > away). I think this is caused by either interrupt #46 or #47 on this system
> > which is on the second 'bank'.
> 
> I resorted to printf debugging, it is IRQ 56 which is the IRQ_GPIOBNK0.. so I
> wonder if this IRQ should end up in the GC GPIO code at all?

That depends on davinci_soc_info.intc_irq_num.

#define DAVINCI_N_AINTC_IRQ     64
#define DA830_N_CP_INTC_IRQ     96
#define TNETV107X_N_CP_INTC_IRQ                 96

No idea which one applies to your machine, but for all in tree boards
56 is in the range of intc interrupts.

Thanks,

	tglx

  reply	other threads:[~2011-06-06 14:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 12:41 TI-Davinci 6446 oops on interrupts Holger Freyther
2011-06-06 13:40 ` Holger Hans Peter Freyther
2011-06-06 14:54   ` Thomas Gleixner [this message]
2011-06-06 15:10     ` Holger Freyther
2011-06-06 15:25       ` Thomas Gleixner
2011-06-06 15:32         ` Holger Freyther
2011-06-06 21:31           ` Thomas Gleixner
2011-06-06 22:50             ` Kevin Hilman
2011-06-07 18:13             ` Nori, Sekhar
2011-06-07 22:59               ` Thomas Gleixner
2011-06-10 18:47         ` Holger Freyther
2011-06-06 14:49 ` Thomas Gleixner
2011-06-06 16:32   ` Russell King - ARM Linux
2011-06-06 17:45     ` Holger Freyther
2011-06-06 17:50       ` Thomas Gleixner
2011-06-06 21:30     ` Thomas Gleixner
2011-06-06 16:30 ` Russell King - ARM Linux

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=alpine.LFD.2.02.1106061650210.13964@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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