From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ARM: s5pv310: update IRQ combiner to use EOI in parent chip
Date: Wed, 23 Feb 2011 15:58:52 -0000 [thread overview]
Message-ID: <001f01cbd372$91f49990$b5ddccb0$@deacon@arm.com> (raw)
In-Reply-To: <AANLkTimiPEsb_S3tv+yPOr=p8UageK_-er9HkjM10ro5@mail.gmail.com>
Hi Kyungmin,
> Tested-by: Kyungmin Park <kyungmin.park@samsung.com>
>
> It's boot and working at mainline.
Thanks for testing this.
> It's just for record.
> Current mainline codes doesn't have full features of s5pv310 (aka
> s5pc210 or exynos4210).
> So I back-ported the same codes to 2.6.36. it's booted and working at
> boot time, but some times later it's hang.
> no serial. I think as irq cores at arm changed, it requires the more
> patched than just this patch.
Interesting. I backported to v2.6.36 and stress-tested it for a few
hours on my versatile express without any problems. If you diagnose
this further, please let me know.
Will
next prev parent reply other threads:[~2011-02-23 15:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 15:28 [PATCH 0/5] Migrate GIC to fasteoi flow control Will Deacon
2011-02-21 15:28 ` [PATCH 1/5] ARM: gic: use handle_fasteoi_irq for SPIs Will Deacon
2011-02-21 15:28 ` [PATCH 2/5] ARM: omap: update GPIO chained IRQ handler to use EOI in parent chip Will Deacon
2011-02-21 19:15 ` Santosh Shilimkar
2011-02-22 14:14 ` Santosh Shilimkar
2011-02-22 18:30 ` Will Deacon
2011-02-22 18:18 ` Tony Lindgren
2011-02-22 18:32 ` Will Deacon
2011-02-21 15:28 ` [PATCH 3/5] ARM: tegra: " Will Deacon
2011-02-22 19:09 ` Colin Cross
2011-02-22 19:21 ` Will Deacon
2011-02-22 19:52 ` Russell King - ARM Linux
2011-02-23 10:39 ` Will Deacon
2011-02-21 15:28 ` [PATCH 4/5] ARM: s5pv310: update IRQ combiner " Will Deacon
2011-02-23 6:59 ` Kyungmin Park
2011-02-23 15:58 ` Will Deacon [this message]
2011-02-21 15:28 ` [PATCH 5/5] ARM: msm: update GPIO chained IRQ handler " Will Deacon
2011-02-24 0:22 ` Abhijeet Dharmapurikar
2011-02-24 12:40 ` Thomas Gleixner
2011-02-24 14:12 ` Will Deacon
2011-02-24 15:42 ` Thomas Gleixner
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='001f01cbd372$91f49990$b5ddccb0$@deacon@arm.com' \
--to=will.deacon@arm.com \
--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).