| commit | a94cc4e6c0a26a7c8f79a432ab2c89534aa674d5 | |
| author | Kirill A. Shutemov <kirill.shutemov@linux.intel.com> | |
| Fri, 26 Aug 2011 11:20:59 +0000 (26 12:20 +0100) | ||
| committer | Linus Torvalds <torvalds@linux-foundation.org> | |
| Fri, 26 Aug 2011 16:03:29 +0000 (26 09:03 -0700) | ||
| tree | c49bd80e9001f189c8f3b3c77518c3cbbb1fc6b9 | treesnapshot (tar.gz zip) |
| parent | 1e8d4e8be2e104514564983239af9dd9521c7779 | commitdiff |
sfi: table irq 0xFF means 'no interrupt'
According to the SFI specification irq number 0xFF means device has no
interrupt or interrupt attached via GPIO.
Currently, we don't handle this special case and set irq field in
*_board_info structs to 255. It leads to confusion in some drivers.
Accelerometer driver tries to register interrupt 255, fails and prints
"Cannot get IRQ" to dmesg.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
According to the SFI specification irq number 0xFF means device has no
interrupt or interrupt attached via GPIO.
Currently, we don't handle this special case and set irq field in
*_board_info structs to 255. It leads to confusion in some drivers.
Accelerometer driver tries to register interrupt 255, fails and prints
"Cannot get IRQ" to dmesg.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
| arch/x86/platform/mrst/mrst.c | diffblobblamehistory |