linux-kernel - Re: [PATCH v2] openrisc: irq: use irqchip framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140521200156.GJ8664@titan.lakedaemon.net>
Date:	Wed, 21 May 2014 16:01:56 -0400
From:	Jason Cooper <jason@...edaemon.net>
To:	Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>, linux@...ts.openrisc.net,
	jonas@...thpole.se
Subject: Re: [PATCH v2] openrisc: irq: use irqchip framework

On Wed, May 21, 2014 at 10:50:57PM +0300, 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.
> 
> What would be the best choice here?
> I think I'm leaning towards 1) and I have a tentative patch for that,
> but I wanted to went the question before posting it.

Are there actually three IP blocks here that we may see separately
somewhere else?

thx,

Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/