From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Necip Fazil Yildiran <fazilyildiran@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
paul@pgazz.com, jeho@cs.utexas.edu
Subject: Re: [PATCH] MIPS: remove the obsolete RM7000 extended interrupts handler
Date: Fri, 2 Oct 2020 11:52:48 +0200 [thread overview]
Message-ID: <20201002095248.GA9146@alpha.franken.de> (raw)
In-Reply-To: <alpine.LFD.2.21.2009302342030.333514@eddie.linux-mips.org>
On Thu, Oct 01, 2020 at 12:10:57AM +0100, Maciej W. Rozycki wrote:
> On Wed, 30 Sep 2020, Thomas Bogendoerfer wrote:
>
> > > > not yet;-) I have an RM7000 based system in my basement... I'm also
> > > > not sure, if R7k O2s need that.
> > >
> > > One of the more exotic Malta daughtercards used that too I believe. I'd
> > > have to check the docs. Of course getting hands on such a daughtercard is
> > > another matter, but we continue having RM7000 enabled for the Malta.
> >
> > I've checked interrupts on P6064 and doesn't use the "extented" interrupts.
> > And since O2 uses the same CPU connector for all CPU boards I doubt it
> > it either.
>
> Mind that interrupts can be asserted in the RM7k via an external write
> request too, and I'm fairly sure SGI hardware would use that rather than
> interrupt inputs given that R4000/R4400 SC/MC CPUs only have Int*(0) wired
> and all the remaining interrupts are only available via a processor write.
> Have you checked that?
checked now, IP32 uses a single interrupt pin coming from CRIME ASIC,
so nothing "fanncy" there and no use for the extended RM7k interrupts.
> > What about Malta ?
>
> So this is the CoreBonito64 daughtercard, which can have either an RM5261
> or an RM7061 processor installed. The Int*(9:6) inputs are not mentioned,
> which I take it means unconnected, and ExtRqst* has a pull-up and is
> otherwise wired to a debug connector only. Which makes me conclude this
> feature cannot be used in a standard application with this card.
>
> NB there is another interrupt controller embedded in the Bonito64 system
> controller, which on the CoreBonito64, conversely, can actually be enabled
> with a jumper and used, but it's not usually either.
ok, thanks for the info.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-10-02 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 14:23 [PATCH] MIPS: remove the obsolete RM7000 extended interrupts handler Necip Fazil Yildiran
2020-09-18 13:50 ` Thomas Bogendoerfer
2020-09-30 14:34 ` Maciej W. Rozycki
2020-09-30 21:21 ` Thomas Bogendoerfer
2020-09-30 23:10 ` Maciej W. Rozycki
2020-10-02 9:52 ` Thomas Bogendoerfer [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=20201002095248.GA9146@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=fazilyildiran@gmail.com \
--cc=jeho@cs.utexas.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=paul@pgazz.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