public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: nsekhar@ti•com (Sekhar Nori)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v5 1/7] ARM: davinci, cp_intc: Add irq domain support
Date: Sat, 2 Jun 2012 01:06:41 +0530	[thread overview]
Message-ID: <4FC919C9.6070107@ti.com> (raw)
In-Reply-To: <1338373143-7467-2-git-send-email-hs@denx.de>

Hi Heiko,

On 5/30/2012 3:48 PM, Heiko Schocher wrote:
> Signed-off-by: Heiko Schocher <hs@denx•de>
> Cc: davinci-linux-open-source at linux.davincidsp.com
> Cc: linux-arm-kernel at lists.infradead.org
> Cc: devicetree-discuss at lists.ozlabs.org
> Cc: Grant Likely <grant.likely@secretlab•ca>
> Cc: Sekhar Nori <nsekhar@ti•com>
> Cc: Wolfgang Denk <wd@denx•de>
> Cc: Sergei Shtylyov <sshtylyov@mvista•com>
> 
> ---

On AM18x EVM, with this patch applied and CONFIG_KEYBOARD_GPIO_POLLED=y,
I get warnings of type:

irq 0, desc: c0372950, depth: 1, count: 0, unhandled: 0

->handle_irq():  c00552f8, handle_bad_irq+0x0/0x23c

->irq_data.chip(): c03794e8, 0xc03794e8

->action():   (null)

   IRQ_NOPROBE set

 IRQ_NOREQUEST set


They do not come when CONFIG_KEYBOARD_GPIO_POLLED=n. I am yet to debug
this, but wanted to point out now in case there is anything obvious.

# cat /proc/interrupts
           CPU0

  0:         32      none

 11:          0   cp_intc  edma

 12:          0   cp_intc  edma_error

 15:    1048613   cp_intc  i2c_davinci

 21:      50992   cp_intc  clockevent

 22:         17   cp_intc  free-run counter

 33:          0   cp_intc  eth0

 34:      13747   cp_intc  eth0

 35:       5032   cp_intc  eth0

 36:          0   cp_intc  eth0

 52:     162759   cp_intc  da8xx_lcdc

 61:        270   cp_intc  serial

 93:          0   cp_intc  edma

 94:          0   cp_intc  edma_error

Err:         32


The interrupt number 0 shows up which seems to be causing these warnings.

I also had to select IRQ_DOMAIN for CP_INTC in
arch/arm/mach-davinci/Kconfig to make the kernel builds after applying
this patch.

Thanks,
Sekhar

  reply	other threads:[~2012-06-01 19:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 10:18 [PATCH v5 0/7] ARM: davinci: add support for the am1808 based enbw_cmc board Heiko Schocher
2012-05-30 10:18 ` [PATCH v5 1/7] ARM: davinci, cp_intc: Add irq domain support Heiko Schocher
2012-06-01 19:36   ` Sekhar Nori [this message]
2012-06-12 17:36     ` Sekhar Nori
2012-06-13  9:50       ` Heiko Schocher
2012-06-25 17:15   ` Sekhar Nori
2012-06-26  6:54     ` Heiko Schocher
2012-05-30 10:18 ` [PATCH v5 2/7] ARM: davinci, cp_intc: Add OF support for TI interrupt controller Heiko Schocher
2012-07-03 19:09   ` Sekhar Nori
2012-05-30 10:18 ` [PATCH v5 3/7] ARM: davinci: configure davinci aemif chipselects through OF Heiko Schocher
2012-05-30 10:19 ` [PATCH v5 4/7] ARM: davinci: net: davinci_emac: add OF support Heiko Schocher
2012-07-08 14:26   ` Sekhar Nori
2012-07-09  8:25     ` Heiko Schocher
2012-05-30 10:19 ` [PATCH v5 5/7] ARM: davinci: i2c: " Heiko Schocher
2012-07-13 13:57   ` Sekhar Nori
2012-07-14  4:15     ` Heiko Schocher
2012-07-16 16:16       ` Sekhar Nori
2012-05-30 10:19 ` [PATCH v5 6/7] ARM: mtd: nand: davinci: add OF support for davinci nand controller Heiko Schocher
2012-07-18 17:45   ` Sekhar Nori
2012-05-30 10:19 ` [PATCH v5 7/7] ARM: davinci: add support for the am1808 based enbw_cmc board Heiko Schocher

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=4FC919C9.6070107@ti.com \
    --to=nsekhar@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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