diff options
| author | Octavian Purdila <[email protected]> | 2015-06-05 16:59:43 +0300 |
|---|---|---|
| committer | Alexandre Belloni <[email protected]> | 2015-09-05 13:19:07 +0200 |
| commit | 0d9030a2c3214cf8f9bfff84204e0f5ba5e790d7 (patch) | |
| tree | 5a5d89466e9619ae3fb6bf55c27fcef154e95846 /tools/perf/scripts/python/bin | |
| parent | 1e4cd62558c293bc51cc179d676b708683a29c12 (diff) | |
rtc: fix drivers that consider 0 as a valid IRQ in client->irq
Since dab472eb931b ("i2c / ACPI: Use 0 to indicate that device does not
have interrupt assigned"), 0 is not a valid i2c client irq anymore, so
change all driver's checks accordingly.
The same issue occurs when the device is instantiated via device tree
with no IRQ, or from the i2c sysfs interface, even before the patch
above.
Signed-off-by: Octavian Purdila <[email protected]>
Reviewed-by: Mika Westerberg <[email protected]>
Signed-off-by: Alexandre Belloni <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions