public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
To: Grant Likely <grant.likely@secretlab.ca>,
	linux-kernel@vger.kernel.org,
	alexander.stein@systec-electronic.com
Cc: qi.wang@intel.com, yong.y.wang@intel.com,
	toshiharu-linux@dsn.okisemi.com, kok.howg.ewe@intel.com,
	joel.clark@intel.com
Subject: [RESEND]: RE: [PATCH v2 3/3] pch_gpio: support interrupt function
Date: Tue, 07 Jun 2011 15:00:48 +0900	[thread overview]
Message-ID: <4DEDBE90.3090305@dsn.okisemi.com> (raw)

Hi Grant,

Let me resend again.
I haven't received your answer the following my question yet.

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.

-- 
tomoya
OKI SEMICONDUCTOR CO., LTD.

             reply	other threads:[~2011-06-07  6:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  6:00 Tomoya MORINAGA [this message]
2011-06-07 17:22 ` [RESEND]: RE: [PATCH v2 3/3] pch_gpio: support interrupt function Grant Likely
2011-06-08  2:29   ` Tomoya MORINAGA
2011-06-08 14:57     ` Grant Likely
2011-06-09  1:29       ` Tomoya MORINAGA
2011-06-20  1:07   ` Tomoya MORINAGA
2011-06-20  4:25     ` Grant Likely

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=4DEDBE90.3090305@dsn.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