[<prev] [next>] [day] [month] [year] [list]
Message-ID: <4C58ADF4.8070201@am.sony.com>
Date: Tue, 3 Aug 2010 17:01:56 -0700
From: Frank Rowand <frank.rowand@...sony.com>
To: Thomas Gleixner <tglx@...utronix.de>
CC: peterz@...radead.org, peter.p.waskiewicz.jr@...el.com,
mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: [PATCH RESEND] genirq: update comments related to buslock support
Update comments to match code change in 70aedd24
Signed-off-by: Frank Rowand <frank.rowand@...sony.com>
---
kernel/irq/manage.c | 7 5 + 2 - 0 !
1 file changed, 5 insertions(+), 2 deletions(-)
Index: b/kernel/irq/manage.c
===================================================================
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -236,7 +236,8 @@ void __disable_irq(struct irq_desc *desc
* Unlike disable_irq(), this function does not ensure existing
* instances of the IRQ handler have completed before returning.
*
- * This function may be called from IRQ context.
+ * This function may be called from IRQ context only when
+ * desc->chip->bus_lock and desc->chip->bus_sync_unlock are NULL !
*/
void disable_irq_nosync(unsigned int irq)
{
@@ -264,7 +265,9 @@ EXPORT_SYMBOL(disable_irq_nosync);
* to complete before returning. If you use this function while
* holding a resource the IRQ handler may need you will deadlock.
*
- * This function may be called - with care - from IRQ context.
+ * This function may be called - with care - from IRQ context only when
+ * desc->chip->bus_lock and desc->chip->bus_sync_unlock are NULL !
+ * See synchronize_irq() comments for explanation of "with care".
*/
void disable_irq(unsigned int irq)
{
--
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/
Powered by blists - more mailing lists