From: Tom Rini <trini@kernel•crashing.org>
To: Hans Feldt <Hans.Feldt@uab•ericsson.se>
Cc: Shen Rong <rshen@udtech•com.cn>, linuxppc-embedded@lists•linuxppc.org
Subject: Re: 8260 - Spurious interrupts again
Date: Thu, 19 Dec 2002 10:02:01 -0700 [thread overview]
Message-ID: <20021219170201.GD852@opus.bloom.county> (raw)
In-Reply-To: <3DD4D6EE.5000902@uab.ericsson.se>
On Fri, Nov 15, 2002 at 12:13:50PM +0100, Hans Feldt wrote:
> On 11/15/02 09:58 AM, Shen Rong wrote:
>
> > I have the same problem like you, and I added a "sync" at the last
> > line in
> >m8260_mask_and_ack like you, and it solves the ploblem. But it is
> >interesting
> >that if I add a "sync" above the last line, it's also ok, that's
>
> Well its the write to SIMR that needs a sync before enabling external
> interrupts, not the sipnr variable.
>
> >So I think there should be a time delay when we do mask&ack(&following
> >operation maybe).
>
> Don't agree, I believe the missing sync is a bug. I talked a Motorola
> FAE yesterday and he says the same thing. It doesn't really matter if
> you have the 8260 as a slave or not.
>
> What does the maintainers of this code (Tom Rini?) think about it?
Sorry it took so long to get back to this thread, I'm not sure. I don't
think I know enough about this code to say either way. But I'm inclined
to think the sync is needed regardless as well.
If someone would post a patch vs current linuxppc_2_4 and linuxppc-2.5,
I'll apply it as there definatly seems to be a problem here.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-12-19 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 13:34 8260 - Spurious interrupts again Hans Feldt
2002-11-15 8:58 ` Shen Rong
2002-11-15 11:13 ` Hans Feldt
2002-12-19 17:02 ` Tom Rini [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=20021219170201.GD852@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=Hans.Feldt@uab$(echo .)ericsson.se \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=rshen@udtech$(echo .)com.cn \
/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