All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	swarren@nvidia.com
Subject: Re: [PATCH V2 RESEND 1/2] regmap: irq: Add support for interrupt type
Date: Tue, 12 Mar 2013 19:55:46 +0000	[thread overview]
Message-ID: <20130312195546.GH19942@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1362673997-6762-2-git-send-email-ldewangan@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

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?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-12 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 16:33 [PATCH V2 RESEND 2/2] regmap: irq: do not write mask register if it is not supported Laxman Dewangan
2013-03-07 16:33 ` [PATCH V2 RESEND 1/2] regmap: irq: Add support for interrupt type Laxman Dewangan
2013-03-12 19:55   ` Mark Brown [this message]
2013-03-16 14:46     ` Laxman Dewangan
2013-03-12 19:35 ` [PATCH V2 RESEND 2/2] regmap: irq: do not write mask register if it is not supported Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130312195546.GH19942@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.