From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: "'Grant Likely'" <grant.likely@secretlab.ca>
Cc: <linux-kernel@vger.kernel.org>,
<alexander.stein@systec-electronic.com>, <qi.wang@intel.com>,
<yong.y.wang@intel.com>, <joel.clark@intel.com>,
<kok.howg.ewe@intel.com>, <toshiharu-linux@dsn.okisemi.com>
Subject: RE: [PATCH v2 3/3] pch_gpio: support interrupt function
Date: Fri, 27 May 2011 17:28:25 +0900 [thread overview]
Message-ID: <1AE0D718B2974BCBA409AF045602867F@hacdom.okisemi.com> (raw)
In-Reply-To: <20110527070833.GA31953@ponder.secretlab.ca>
Hi Grant,
On Friday, May 27, 2011 4:09 PM, Grant Likely wrote:
> Take a look at the new irq_chip_generic infrastructure. You
> don't need to implement a memory mapped irq controller from
> scratch anymore.
> Most of the access functions can be taken directly from
> irq_chip_generic instead.
Let me clarify your saying.
a) We shouldn't use request_irq( ) ?
b) Does Your "irq_chip_generic" mean irq_set_handler_data( ) / irq_set_chained_handler( ) ?
If yes, Using these functions, I saw IRQ shared other function's interrupt becomes invalid.
With Best Regards,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.
prev parent reply other threads:[~2011-05-27 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 5:04 [PATCH v2 1/3] pch_gpio: add EG20T PCH GPIO device definition Tomoya MORINAGA
2011-05-27 5:04 ` [PATCH v2 2/3] pch_gpio: Support new device ML7223 Tomoya MORINAGA
2011-05-27 5:04 ` [PATCH v2 3/3] pch_gpio: support interrupt function Tomoya MORINAGA
2011-05-27 7:08 ` Grant Likely
2011-05-27 8:28 ` Tomoya MORINAGA [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=1AE0D718B2974BCBA409AF045602867F@hacdom.okisemi.com \
--to=tomoya-linux@dsn.okisemi.com \
--cc=alexander.stein@systec-electronic.com \
--cc=grant.likely@secretlab.ca \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=toshiharu-linux@dsn.okisemi.com \
--cc=yong.y.wang@intel.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®