From: masami.hiramatsu.pt@hitachi•com (Masami Hiramatsu)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH for 3.9-rc] arm: mvebu: Use local interrupt only for the timer 0
Date: Thu, 21 Mar 2013 11:19:31 +0900 [thread overview]
Message-ID: <514A6E33.6060600@hitachi.com> (raw)
In-Reply-To: <1363792175-3136-1-git-send-email-gregory.clement@free-electrons.com>
(2013/03/21 0:09), Gregory CLEMENT wrote:
> The commit 3a6f08a37 "arm: mvebu: Add support for local interrupt",
> managed the 28th first interrupts as local interrupt to match the
> hardware specification. Among these interrupts there are the Gigabits
> Ethernet ones used by the mvneta driver. Unfortunately the state of
> the percpu_irq API prevents the driver to use it.
>
> Indeed the interrupts have to be freed when the .stop() function is
> called. As the free_percpu_irq() function don't disable the interrupt
> line, we have to do it on each CPU before calling this. The function
> disable_percpu_irq() only disable the percpu on the current CPU and
> there is no function which allows to disable a percpu irq on a given
> CPU. Waiting for the extension of the percpu_irq API, this fix allows
> to use again the mvneta driver.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons•com>
Hi,
I've tested this too.
Tested-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi•com>
Thank you!
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt at hitachi.com
next prev parent reply other threads:[~2013-03-21 2:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 15:09 [PATCH for 3.9-rc] arm: mvebu: Use local interrupt only for the timer 0 Gregory CLEMENT
2013-03-20 15:37 ` Thomas Petazzoni
2013-03-20 16:44 ` Ryan Press
2013-03-20 17:27 ` Thomas Petazzoni
2013-03-20 23:57 ` Ryan Press
2013-03-21 2:19 ` Masami Hiramatsu [this message]
2013-03-26 16:00 ` Thomas Petazzoni
2013-03-26 22:43 ` Jason Cooper
2013-03-27 6:48 ` Gregory CLEMENT
2013-03-28 16:49 ` Jason Cooper
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=514A6E33.6060600@hitachi.com \
--to=masami.hiramatsu.pt@hitachi$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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