From: Jonas Bonn <jonas@southpole.se>
To: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux <linux@openrisc.net>, Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4] openrisc: irq: use irqchip framework
Date: Fri, 30 May 2014 13:08:10 +0200 [thread overview]
Message-ID: <5388669A.2090807@southpole.se> (raw)
In-Reply-To: <20140529202806.GA9387@chokladfabriken.org>
On 05/29/2014 10:28 PM, Stefan Kristiansson wrote:
> On Tue, May 27, 2014 at 08:47:36AM +0200, Jonas Bonn wrote:
>> On 05/26/2014 10:52 PM, Geert Uytterhoeven wrote:
>>> CC devicetree for the bindings
>>>
>>> On Mon, May 26, 2014 at 10:31 PM, Stefan Kristiansson
>>> <stefan.kristiansson@saunalahti.fi> wrote:
>>>> +++ b/Documentation/devicetree/bindings/interrupt-controller/opencores,or1k-pic.txt
>>>> @@ -0,0 +1,23 @@
>>>> +OpenRISC 1000 Programmable Interrupt Controller
>>>> +
>>>> +Required properties:
>>>> +
>>>> +- compatible : should be "opencores,or1k-pic-level" for variants with
>>>> + level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
>>>> + edge triggered interrupt lines or "opencores,or1200-pic" for machines
>>>> + with the non-spec compliant or1200 type implementation.
>>>> +
>>>> + "opencores,or1k-pic" is also provided as an alias to "opencores,or1200-pic",
>>>> + but this is only for backwards compatibility.
>>
>> I still think this identifier needs to be versioned. Use the same
>> version number as we have on the cpu identifier since the OR1200 PIC
>> hasn't changed since then; i.e. opencores,or1200-pic-rtlsvnXYZ.
>>
>
> I can change that if you *really* insist on it...
> But I don't understand the purpose of the versioning here,
> there will never be any other or1200-pic version than the one that currently
> exists, so IMO "or1200" should be enough versioning information.
Famous last words... ;)
It has been insisted upon earlier by upstream; for example, when we
submitted the openrisc architecture. Aside from that, I am not the one
who is going to be doing any insisting here.
That said, given that this is a soft core CPU and what that entails, I
do think it is probably a good idea to version this thing.
Hopefully you will get some sage advice from someone else here...
otherwise, you may do as you see fit.
Your patch is otherwise fine by me and your effort here is much appreciated!
Acked-by: Jonas Bonn <jonas@southpole.se>
/Jonas
next prev parent reply other threads:[~2014-05-30 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 20:31 [PATCH v4] openrisc: irq: use irqchip framework Stefan Kristiansson
2014-05-26 20:52 ` Geert Uytterhoeven
2014-05-27 6:47 ` Jonas Bonn
2014-05-29 20:28 ` Stefan Kristiansson
2014-05-30 11:08 ` Jonas Bonn [this message]
2014-06-21 2:04 ` Jason Cooper
2014-06-21 7:13 ` Stefan Kristiansson
2014-06-21 20:02 ` Jason Cooper
2014-07-01 12:25 ` 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=5388669A.2090807@southpole.se \
--to=jonas@southpole.se \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--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