linux-kernel - [PATCH] kernel: irq: Call irq_chip->irq_mask in irq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 9 Jul 2013 19:56:47 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	<tglx@...utronix.de>
CC:	<linux-kernel@...r.kernel.org>,
	sreenivasulu velpula <svelpula@...dia.com>,
	Laxman Dewangan <ldewangan@...dia.com>
Subject: [PATCH] kernel: irq: Call irq_chip->irq_mask in irq_disable

From: sreenivasulu velpula <svelpula@...dia.com>

If interrupt driver has implemented the irq_mask/irq_unmask
callbacks for disable/enable interrupt then call these APIs
from irq_disable/irq_enable.

Currently, on irq_disable(), it just look for the callback
irq_disable() implemented by chip interrupt driver not the
irq_mask().

Add check for the valid callback of irq_mask() and if it is
there then call it from irq_disable.

This is based on change done by:
	sreenivasulu velpula <svelpula@...dia.com>

Signed-off-by: sreenivasulu velpula <svelpula@...dia.com>
Signed-off-by: Laxman Dewangan <ldewangan@...dia.com>
---
 kernel/irq/chip.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index a3bb14f..b6efb92 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -232,6 +232,9 @@ void irq_disable(struct irq_desc *desc)
 	if (desc->irq_data.chip->irq_disable) {
 		desc->irq_data.chip->irq_disable(&desc->irq_data);
 		irq_state_set_masked(desc);
+	} else if (desc->irq_data.chip->irq_mask) {
+		desc->irq_data.chip->irq_mask(&desc->irq_data);
+		irq_state_set_masked(desc);
 	}
 }
 
-- 
1.7.1.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/