linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ata: Don't use NO_IRQ in pata_of_platform driver
Date: Tue, 06 Dec 2011 13:56:00 -0600	[thread overview]
Message-ID: <4EDE7350.4010104@gmail.com> (raw)
In-Reply-To: <20111206114952.GS14542@n2100.arm.linux.org.uk>

On 12/06/2011 05:49 AM, Russell King - ARM Linux wrote:
> On Tue, Dec 06, 2011 at 11:37:35AM +0000, Dave Martin wrote:
>> 1) All OF code and drivers should be migrating to use 0 instead of NO_IRQ
>>    for the no-interrupt case.  Code which receives irq numbers directly
>>    from the OF framework and refers to NO_IRQ, or expects 0 to be a valid
>>    needs to be fixed.
>>
>> 2) Where we hit a problem, board code needs to be adapted to remap HW IRQs
>>    0-15 to different software values.  (This could be done using irq
>>    domains, or not)
> 
> No AMBA driver I'm aware of ever uses an IRQ number 0 or is passed such
> an IRQ number.

The watchdog on VersatileAB is on Linux IRQ0. This is easily fixed with
VIC irqdomain patches which are queued up.

Rob

  parent reply	other threads:[~2011-12-06 19:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111110162859.GA7088@oksana.dev.rtsoft.ru>
     [not found] ` <20111202192618.GC3037@localhost.localdomain>
2011-12-02 19:28   ` [PATCH] ata: Don't use NO_IRQ in pata_of_platform driver Linus Torvalds
2011-12-02 23:12     ` Benjamin Herrenschmidt
2011-12-05 16:11       ` Dave Martin
2011-12-05 17:40         ` Nicolas Pitre
2011-12-05 18:02           ` Dave Martin
2011-12-05 18:15             ` Geert Uytterhoeven
2011-12-05 18:18             ` Nicolas Pitre
2011-12-05 18:45               ` Alan Cox
2011-12-05 19:19                 ` James Bottomley
2011-12-06  6:13                 ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-06 11:34                   ` Alan Cox
2011-12-05 19:16               ` Rob Herring
2011-12-05 20:21                 ` Anton Vorontsov
2011-12-05 20:47                   ` Rob Herring
2011-12-05 20:53                     ` Alan Cox
2011-12-06  9:30                     ` Dave Martin
2011-12-06 10:34                       ` Alan Cox
2011-12-06 10:55                       ` Russell King - ARM Linux
2011-12-05 19:26               ` Dave Martin
2011-12-05 19:49                 ` Nicolas Pitre
2011-12-06  9:37                   ` Dave Martin
2011-12-06 10:46                     ` Russell King - ARM Linux
2011-12-06 11:00                       ` Geert Uytterhoeven
2011-12-06 11:03                         ` Russell King - ARM Linux
2011-12-06 11:10                         ` Alan Cox
2011-12-06 11:05                       ` Alan Cox
2011-12-06 11:25                         ` Russell King - ARM Linux
2011-12-06 12:11                           ` Alan Cox
2011-12-06 11:37                       ` Dave Martin
2011-12-06 11:49                         ` Russell King - ARM Linux
2011-12-06 13:25                           ` Dave Martin
2011-12-06 19:56                           ` Rob Herring [this message]
2011-12-06 19:20                       ` Linus Torvalds
2011-12-06 20:00                         ` Russell King - ARM Linux
2011-12-06 20:59                         ` Uwe Kleine-König
2011-12-06 19:11                     ` Nicolas Pitre
2011-12-05 17:41         ` Alan Cox

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=4EDE7350.4010104@gmail.com \
    --to=robherring2@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).