linux-kernel - Re: [PATCH 1/1] irq: get_irq_disable

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-prev] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.02.1303261210230.22263@ionos>
Date:	Tue, 26 Mar 2013 12:14:29 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andreas Fenkart <andreas.fenkart@...eamunlimited.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] irq: get_irq_disable_depth.

On Mon, 25 Mar 2013, Andreas Fenkart wrote:
> Used to verify invariant in omap_hsmmc, were a gpio is used to detect
> sdio irqs during suspend phase. The ref count from irq_enable/irq_disable
> is used to control when the irq should be effectively enabled.
> 
>                  irq en     irq dis
>             ------------------------
>   pm suspend  |    0     |   1
>   pm default  |    1     |   2
> 
>               irq disable depth
> 
> When the sdio irq is enabled AND the module is in runtime suspend,
> the ref must be zero so the irq is effectively enabled.
> 
> This function helps to verify, that the disable depth has the
> right value at different driver states.

I'm really not getting it. The SDIO driver knows whether it has
interrupts enabled or not, so what needs to be verified?

If you need this just to debug your driver, then please keep it in
your private tree. I really can't see a general value for this.

Thanks,

	tglx
--
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/