From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] regmap: irq: Add support for interrupt type
Date: Thu, 14 Feb 2013 11:06:40 +0000 [thread overview]
Message-ID: <20130214110640.GB13249@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <511CC41E.7040608@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On Thu, Feb 14, 2013 at 04:31:50PM +0530, Laxman Dewangan wrote:
> is this mean we should have variable like
> .supported_iflags which capture what it is supported or not.
> And then irq_type_val[MAX_REGMAP_IRQ_TYPE] as array and define the
> REGMAP_IRQ_TYPE_[FALLING/RISING/BOTH] as index and client can fill
> this info as per the hardware or
I think this option is best; it's going to avoid us having to write
explicit cases for every single use case. But perhaps it's going to be
too painful to work with.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-02-14 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 13:14 [PATCH 1/2] regmap: irq: Add support for interrupt type Laxman Dewangan
2013-02-13 13:14 ` [PATCH 2/2] regmap: irq: do not write mask register if it is not supported Laxman Dewangan
2013-02-13 14:20 ` Mark Brown
2013-02-14 11:06 ` Laxman Dewangan
2013-02-14 11:35 ` Mark Brown
2013-02-14 11:55 ` Laxman Dewangan
2013-02-14 11:57 ` Mark Brown
2013-02-14 12:16 ` Laxman Dewangan
2013-02-13 13:54 ` [PATCH 1/2] regmap: irq: Add support for interrupt type Mark Brown
2013-02-14 11:01 ` Laxman Dewangan
2013-02-14 11:06 ` Mark Brown [this message]
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=20130214110640.GB13249@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox