linux-kernel - Re: [PATCH 2/2] regmap: irq: do not write mask register if it is not supported

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130214115746.GF13249@opensource.wolfsonmicro.com>
Date:	Thu, 14 Feb 2013 11:57:47 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] regmap: irq: do not write mask register if it is not
 supported

On Thu, Feb 14, 2013 at 05:25:13PM +0530, Laxman Dewangan wrote:
> On Thursday 14 February 2013 05:05 PM, Mark Brown wrote:

> >This doesn't sound like something that should be open coded in
> >individual interrupt controller drivers, obviously it's a bit rubbish
> >that there's no way to enable or disable the interrupt but presumably
> >other hardware has the same "feature" and the IRQ subsystem ought to
> >understand it.

> To support such case, can we assume that mask is always enabled
> (interrupt enabled) so that it can be use in irq_thread to mask the
> interrupt status. So during initialization, if there is no mask_base
> register then all mask_buf is such that it enabled interrupt.

...and have any attempt to mask the interrupt return an error?

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)