From: Tero Kristo <t-kristo@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, khilman@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 1/6] ARM: OMAP3: PRM: move prcm interrupt handlers to PRM driver code
Date: Mon, 16 Jul 2012 14:41:06 +0300 [thread overview]
Message-ID: <1342438866.4672.62.camel@sokoban> (raw)
In-Reply-To: <5003FA61.2050003@ti.com>
On Mon, 2012-07-16 at 16:56 +0530, Rajendra Nayak wrote:
> On Friday 13 July 2012 10:07 PM, Tero Kristo wrote:
> > PM code doesn't really care about the PRCM wakeup + io interrupts on
> > OMAP3, as these are used only for acking PRCM internal events, and the
> > IO chain handler is taken care of by hwmod code. Thus move the interrupt
> > handling logic from pm34xx.c to prm2xxx_3xxx.c file. This patch also
> > includes a minor cleanup for removing the priority handling and replacing
> > it with a mechanism for acking pending events. This gets rid of the need
> > for registering the shared interrupt handlers in specific order.
>
> It would be easier to review if you were to split this into 2 patches,
> one which moves functions around as-is and another which does the
> cleanup/optimization. Having both in one is kinda hard to review.
The code was like that originally, however it was broken without the
cleanup / optimization. Simply moving the code around caused a problem
with idle: the sequencing of the interrupt handlers for IO event were
reversed and thus IO chain events for UARTs were never detected (they
were acked before parsing the chain.) Having these two things in
separate patches would introduce a bisect breakage for idle.
-Tero
next prev parent reply other threads:[~2012-07-16 11:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 16:37 [RFC 0/6] ARM: OMAP3+: minor PM core code cleanup Tero Kristo
2012-07-13 16:37 ` [RFC 1/6] ARM: OMAP3: PRM: move prcm interrupt handlers to PRM driver code Tero Kristo
2012-07-16 11:26 ` Rajendra Nayak
2012-07-16 11:41 ` Tero Kristo [this message]
2012-07-31 0:31 ` Kevin Hilman
2012-08-07 7:28 ` Tony Lindgren
2012-07-13 16:37 ` [RFC 2/6] ARM: OMAP3: clock data: prevent IVA2 DPLL low power stop mode Tero Kristo
2012-07-13 16:37 ` [RFC 3/6] ARM: OMAP3: hwmod data: fix iva2 reset info Tero Kristo
2012-07-16 0:12 ` Paul Walmsley
2012-07-13 16:37 ` [RFC 4/6] ARM: OMAP3: hwmod data: add custom setup_preprogram for iva hwmod Tero Kristo
2012-07-13 16:37 ` [RFC 5/6] ARM: OMAP3: hwmod data: add sad2d hwmod Tero Kristo
2012-07-16 1:14 ` Paul Walmsley
2012-07-16 1:28 ` Paul Walmsley
2012-07-13 16:37 ` [RFC 6/6] ARM: OMAP3: hwmod data: add custom setup_preprogram for " Tero Kristo
2012-07-30 20:53 ` [RFC 0/6] ARM: OMAP3+: minor PM core code cleanup Kevin Hilman
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=1342438866.4672.62.camel@sokoban \
--to=t-kristo@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.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