From: Jason Cooper <jason@lakedaemon.net>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 3/3] irqchip: orion: reverse irq handling priority
Date: Mon, 28 Apr 2014 16:59:11 -0400 [thread overview]
Message-ID: <20140428205911.GC28159@titan.lakedaemon.net> (raw)
In-Reply-To: <535EB4C1.9090603@gmail.com>
On Mon, Apr 28, 2014 at 10:06:25PM +0200, Sebastian Hesselbarth wrote:
> On 04/28/2014 09:39 PM, Thomas Gleixner wrote:
> > On Sat, 26 Apr 2014, Sebastian Hesselbarth wrote:
> >
> >> Non-DT irq handlers were working through irq causes from most-significant
> >> to least-significant bit, while DT irqchip driver does it the other way
> >> round. This revealed some more HW issues on Kirkwood peripheral IP, where
> >> spurious sdio irqs can happen although IP's irq enable registers are all
> >> zero. Although, not directly related with the described issue, reverse
> >> irq bit handling back to original order by replacing ffs() with fls().
> >
> > So why are we reverting to the original order?
> >
> > The explanation above is just confusing.
>
> Actually, I first wanted to reply "The original order worked for
> years, so get back to it." But then I thought about finding a better
> answer and remembered some comment of Russell a while ago.
>
> I disassembled the generated binary and the original order saves two
> instructions for each bit count using clz.
>
> With this patch:
> 60: e3a07001 mov r7, #1
> 64: e16f3f14 clz r3, r4
> 68: e263301f rsb r3, r3, #31
> 6c: e1c44317 bic r4, r4, r7, lsl r3
> 70: e5951004 ldr r1, [r5, #4]
>
> Without this patch:
> 60: e3a06001 mov r6, #1
> 64: e2643000 rsb r3, r4, #0
> 68: e0033004 and r3, r3, r4
> 6c: e16f3f13 clz r3, r3
> 70: e263301f rsb r3, r3, #31
> 74: e1c44316 bic r4, r4, r6, lsl r3
> 78: e5971004 ldr r1, [r7, #4]
> You want me to reword the commit message accordingly?
Please do. I would even quote the above.
thx,
Jason.
next prev parent reply other threads:[~2014-04-28 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 19:34 [PATCH RESEND 0/3] Orion irqchip and Kirkwood SDIO Sebastian Hesselbarth
2014-04-26 19:34 ` [PATCH RESEND 1/3] mmc: mvsdio: silence card detect notice Sebastian Hesselbarth
2014-04-28 11:02 ` Ulf Hansson
2014-04-26 19:34 ` [PATCH RESEND 2/3] mmc: mvsdio: workaround for spurious irqs Sebastian Hesselbarth
2014-04-28 11:02 ` Ulf Hansson
2014-04-26 19:34 ` [PATCH RESEND 3/3] irqchip: orion: reverse irq handling priority Sebastian Hesselbarth
2014-04-28 19:39 ` Thomas Gleixner
2014-04-28 20:06 ` Sebastian Hesselbarth
2014-04-28 20:59 ` Jason Cooper [this message]
2014-04-28 21:12 ` [PATCH v2 " Sebastian Hesselbarth
2014-05-05 0:10 ` 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=20140428205911.GC28159@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®