From: Jonas Bonn <jonas@southpole.se>
To: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux@openrisc.net, Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH v2] openrisc: irq: use irqchip framework
Date: Thu, 22 May 2014 09:32:05 +0200 [thread overview]
Message-ID: <537DA7F5.6010704@southpole.se> (raw)
In-Reply-To: <20140521195056.GA14701@chokladfabriken.org>
On 05/21/2014 09:50 PM, Stefan Kristiansson wrote:
>
> I see two paths to go to get there though, and here's where I'd like some input.
> 1) Define the three different implementations as seperate irqchips,
> with accompanying IRQCHIP_DECLARE.
> 2) Add custom device-tree bindings and determine the chip type from that.
I think 1) above is the way to go. Something alone the lines of
"opencores,or1k-pic-level", "opencores,or1k-pic-edge", and
"opencores,or1200-pic".
The first two match the behaviour of the or1k specification; the third
one, however, is really a misimplementation of the spec and is kind of
tied to the actual implementation of the OR1200... I wonder if we don't
need to version this one like we version the CPU identifier (*-rtlsvnXXXXX).
/Jonas
next prev parent reply other threads:[~2014-05-22 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 20:11 [PATCH v2] openrisc: irq: use irqchip framework Stefan Kristiansson
2014-05-19 23:18 ` Thomas Gleixner
2014-05-21 19:50 ` Stefan Kristiansson
2014-05-21 20:01 ` Jason Cooper
2014-05-21 20:23 ` Stefan Kristiansson
2014-05-22 7:32 ` Jonas Bonn [this message]
2014-05-22 7:48 ` [ORLinux] " Geert Uytterhoeven
2014-05-22 19:58 ` Stefan Kristiansson
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=537DA7F5.6010704@southpole.se \
--to=jonas@southpole.se \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@openrisc.net \
--cc=stefan.kristiansson@saunalahti.fi \
--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