public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ata: Don't use NO_IRQ in pata_of_platform driver
Date: Mon, 5 Dec 2011 18:02:53 +0000	[thread overview]
Message-ID: <20111205180253.GB29812@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.02.1112051236350.2357@xanadu.home>

On Mon, Dec 05, 2011 at 12:40:16PM -0500, Nicolas Pitre wrote:
> On Mon, 5 Dec 2011, Dave Martin wrote:
> > On Sat, Dec 03, 2011 at 10:12:53AM +1100, Benjamin Herrenschmidt wrote:
> > > On Fri, 2011-12-02 at 11:28 -0800, Linus Torvalds wrote:
> > > > Don't *change* NO_IRQ to zero (that whole #define is broken - leave it
> > > > around as a marker of brokenness), just start removing it from all the
> > > > ARM drivers that use the OF infrastructure. Which is presumably not
> > > > all that many yet.
> > > > 
> > > > So whenever you find breakage, the fix now is to just remove NO_IRQ
> > > > tests, and replace them with "!irq".
> > > 
> > 
> > Russell, do you know whether it would make sense to set a timeline for 
> > removing NO_IRQ from ARM platforms and migrating to 0 for the no-interrupt
> > case?  I'm assuming that this mainly involves migrating existing hard-wired
> > code that deals with interrupt numbers to use irq domains.
> 
> How many drivers do use IRQ #0 to start with?  We might discover that in 
> practice there is only a very few cases where this is an issue if 0 
> would mean no IRQ.

The total number of files referring to NO_IRQ is not that huge:

arch/arm/	188 matches in 39 files
drivers/	174 matches in 84 files

Unfortunately, NO_IRQ is often not spelled "NO_IRQ".  It looks like the assumption
"irq < 0 === no irq" may be quite a lot more widespread than "NO_IRQ === no irq".
Since there's no specific thing we can grep for (and simply due to volume)
finding all such instances may be quite a bit harder.

For example, git grep 'irq.*\(>=\|<[^=]\) *0' gives

drivers/	435 matches in 314 files
arch/arm/	18 matches in 15 files

A few examples:
drivers/input/mouse/pxa930_trkball.c:   if (irq < 0) {
drivers/input/keyboard/tegra-kbc.c:     if (irq < 0) {
drivers/crypto/omap-sham.c:     if (dd->irq >= 0)

...etc., etc., although there are probably a fair number of false positives here.


whereas git grep 'irq.*\(<\|>\|<=\|>=\|==\|!=\) \+-1' gives

drivers/	68 matches in 28 files
arch/arm/	18 matches in 15 files

Examples: 


...and that's just the code which is C and is also kind enough to put
irq numbers in variables with names containing "irq".

It also doesn't catch people initialising variables or struct/array
members to -1, unadorned "-1" arguments to functions and so on... though
those are likely to appear in mostly the same files matching the above
expressions, it won't be an exact 1:1 correspondence.


Cheers
---Dave

  reply	other threads:[~2011-12-05 18:02 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 [this message]
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
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=20111205180253.GB29812@localhost.localdomain \
    --to=dave.martin@linaro.org \
    --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