linux-kernel - Re: [PATCH 1/2] regmap-irq: use mask and val rather than using mask_buf

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: <20120720095627.GO4495@opensource.wolfsonmicro.com>
Date:	Fri, 20 Jul 2012 10:56:27 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	"Kim, Milo" <Milo.Kim@...com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] regmap-irq: use mask and val rather than using
 mask_buf_def

On Fri, Jul 20, 2012 at 07:08:15AM +0000, Kim, Milo wrote:

Fix your mailer to word wrap within paragraphs, I have reformatted your
mail for legibility.

> Which is better understandable terminology ? 'mask and value' or
> 'default mask and updated mask' I think 'mask & value' is more clear.

But you need to say which value we're talking about - there's multiple
values we're working with here, the interrupt mask is only one of them.
We also have the wake masks and the actual interrupt status values for
example.

> (b) supporting interrupt-unmasked device
> There is different interrupt concept from interrupt-masked device.
> To enable the IRQ, the register bit should be 1.
> To update this value, the bit of IRQ value should be separated from the mask bit.

The variable you're changing isn't the interrupt value, it's the virtual
copy of the mask registers.  The interrupt status value is managed
separately.

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