All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	tglx@linutronix.de
Subject: Re: [PATCH v4] pch_gpio: Support interrupt function
Date: Mon, 11 Jul 2011 17:27:35 +0900	[thread overview]
Message-ID: <4E1AB3F7.2070600@dsn.okisemi.com> (raw)
In-Reply-To: <4E12A69C.8030709@dsn.okisemi.com>

Hi Grant,

(2011/07/05 14:52), Tomoya MORINAGA wrote:
> (2011/07/05 12:59), Grant Likely wrote:
>>> As we discussed before,
>>> without specifying PCH_IRQ_BASE,
>>> it seemed IRQ number collision issue occurred.
>>> Thus, I added PCH_IRQ_BASE.
>>
>> Then fix the irq collision. If the core code hands out an irq range
>> that is in-use by some other driver, then the other driver isn't
>> reserving it's irqs correctly and it needs to be fixed. Hacking
>> around the problem doesn't help anything in the long run.
>>
>
> I tried to work irq_alloc_descs with dynamic allocation.(Set 2nd
> parameter as 0).
> However it seems the issue remains to be seen.
> I attached dmesg output log, /proc/interrupts log and modified PCH-GPIO
> source code.
>
> Could you give me your opinion or information ?
>
> NOTE: I tested on linux-3.0-rc3
>
How is it going ?

-- 
tomoya
OKI SEMICONDUCTOR CO., LTD.

  reply	other threads:[~2011-07-11  8:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01  2:16 [PATCH v4] pch_gpio: Support interrupt function Tomoya MORINAGA
2011-07-04 16:31 ` Grant Likely
2011-07-05  3:52   ` Tomoya MORINAGA
2011-07-05  3:59     ` Grant Likely
2011-07-05  5:52       ` Tomoya MORINAGA
2011-07-11  8:27         ` Tomoya MORINAGA [this message]
2011-07-15 20:14           ` Grant Likely
2011-07-19  8:02             ` Tomoya MORINAGA

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=4E1AB3F7.2070600@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=tglx@linutronix.de \
    --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 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.