From: Mark Brown <broonie@kernel.org>
To: Yi Zhang <yizhang.mrvl@gmail.com>
Cc: Yi Zhang <yizhang@marvell.com>,
hongfeng@marvell.com, linux-kernel@vger.kernel.org,
zhouqiao@marvell.com
Subject: Re: [Question] Should we make the primary interrupt handler configurable for regmap_add_irq_chip()?
Date: Thu, 16 Jan 2014 14:01:53 +0000 [thread overview]
Message-ID: <20140116140153.GC17314@sirena.org.uk> (raw)
In-Reply-To: <CAK=oMXc1YwQcAEfwzgr9QKVCF8kyT3wH2aubYtMYCcJBxviw6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Thu, Jan 16, 2014 at 07:33:13PM +0800, Yi Zhang wrote:
> 2014/1/15 Mark Brown <broonie@kernel.org>:
> > On Sat, Jan 11, 2014 at 12:15:21PM +0800, Yi Zhang wrote:
> >> I met a scenario:
> >> As soon as the interrupt is triggered, a wakelock is needed to be held
> >> until the threaded handler finishes,
> >> I think we may hold it in the primary interrupt handler, but now it's
> >> NULL by default;
> > This sounds like something we should just support in the core, though to
> Sorry, I'm not clear about this, you mean that this has been supported
> in regmap framework?
> I searched but didn't find related mail about this, could you please
> kindly point out the mail loop?
> thanks very much;
I'm saying we should support it in the core rather than providing a way
to override the handlers - it seems like it'll be sufficiently common
that we'll rapidly end up with multiple implementations anyway. It
isn't currently supported in the core though, someone would need to
write that code.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-01-16 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 4:15 Yi Zhang
2014-01-14 21:06 ` Mark Brown
2014-01-16 11:33 ` Yi Zhang
2014-01-16 14:01 ` 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=20140116140153.GC17314@sirena.org.uk \
--to=broonie@kernel.org \
--cc=hongfeng@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yizhang.mrvl@gmail.com \
--cc=yizhang@marvell.com \
--cc=zhouqiao@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®