From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: imx: create temporary irq_desc of #32 irq for GPC operation
Date: Fri, 12 Dec 2014 11:15:39 +0100 [thread overview]
Message-ID: <1418379339.3172.6.camel@pengutronix.de> (raw)
In-Reply-To: <1418363138-19805-1-git-send-email-b20788@freescale.com>
Hi Anson,
Am Freitag, den 12.12.2014, 13:45 +0800 schrieb Anson Huang:
> The irq_get_irq_data may return NULL if irq_data is NOT ready,
> it is fine for now because imx6q_set_lpm is called after all
> irq_data is ready. But in linux-next branch where irq descriptor
> alloc is moved to behind the imx6q_set_lpm called by
> (9a1091e irqchip: gic: Support hierarchy irq domain), below crash
> occurs, as all we need is a irq number passed to GPC module, rather
> than making sure irq_data is ready before imx6q_set_lpm is called,
> let's create a temporary variable of irq_desc for GPC to unmask/mask the
> irq #32 we want, then below issue fixed.
This is already fixed in
e2fd06f6be69 ("ARM: imx: irq: fix buggy usage of irq_data irq field")
65bb688aab94 ("ARM: imx6: fix bogus use of irq_get_irq_data")
regards
Philipp
prev parent reply other threads:[~2014-12-12 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 5:45 [PATCH] arm: imx: create temporary irq_desc of #32 irq for GPC operation Anson Huang
2014-12-12 10:15 ` Philipp Zabel [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=1418379339.3172.6.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).