linux-kernel - Re: [PATCH V2 RESEND 1/2] regmap: irq: Add support for interrupt type

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

Message-ID: <20130312195546.GH19942@opensource.wolfsonmicro.com>
Date:	Tue, 12 Mar 2013 19:55:46 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	swarren@...dia.com
Subject: Re: [PATCH V2 RESEND 1/2] regmap: irq: Add support for interrupt type

On Thu, Mar 07, 2013 at 10:03:17PM +0530, Laxman Dewangan wrote:

>  /**
> + * The Regmap IRQ type Index
> + * REGMAP_IRQ_TYPE_NONE is used for setting inital value for clearing type.
> + */
> +enum {
> +	REGMAP_IRQ_TYPE_NONE,
> +	REGMAP_IRQ_TYPE_RISING,
> +	REGMAP_IRQ_TYPE_FALLING,
> +	REGMAP_IRQ_TYPE_BOTH,
> +	REGMAP_IRQ_TYPE_LEVEL_HIGH,
> +	REGMAP_IRQ_TYPE_LEVEL_LOW,
> +
> +	/* Last entry to get maximum index */
> +	REGMAP_IRQ_TYPE_NR,

Why can't we just use the normal IRQ_TYPE macros?

> + * @type_reg_sub_offset: Suboffset for type register if type mask are
> + *              accomodated in the multiple register.
> + * @type_supported_flags: Supported interrupt type as per interrupt.h.
> + *             All supported flags are ORed.
> + * type_mask: Type mask for getting related register bits.
> + * @type_value: The type value in array form to set value for a given flag.

This is making my head hurt, it's a bit confusing - I'm having to think
too hard to understand what all these different fields do and how they
interact.  Especially type_reg_sub_offset which feels like it must be
part of a wider feature to support a greater range of register layouts.

Can you clarify a bit please?

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