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: Wed, 30 Sep 2020 23:21:31 +0200 [thread overview]
Message-ID: <20200930212131.GA14275@alpha.franken.de> (raw)
In-Reply-To: <alpine.LFD.2.21.2009301529080.333514@eddie.linux-mips.org>
On Wed, Sep 30, 2020 at 03:34:25PM +0100, Maciej W. Rozycki wrote:
> On Fri, 18 Sep 2020, Thomas Bogendoerfer wrote:
>
> > > IRQ_CPU_RM7K has been a non-visible config selected nowhere since
> > > PMC-Sierra Yosemite support has been removed with commit bdf20507da11
> > > ("MIPS: PMC-Sierra Yosemite: Remove support."). By the same token, the
> > > handler for RM7000 extended interrupts has been obsolete.
> > >
> > > Remove the obsolete code.
> >
> > 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. What about Malta ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-09-30 21:21 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 [this message]
2020-09-30 23:10 ` Maciej W. Rozycki
2020-10-02 9:52 ` Thomas Bogendoerfer
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=20200930212131.GA14275@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