Date: Fri, 16 Jan 2015 17:42:09 +0000 From: Julien Grall <julien.grall@linaro.org> To: Svatopluk Kraus <onwahe@gmail.com>, freebsd-arm@freebsd.org, Roger Pau Monne <roger.pau@citrix.com> Subject: Re: interrupt framework Message-ID: <54B94D71.90403@linaro.org> In-Reply-To: <CAFHCsPX5kG_v-F-cjpyMQsT_b386eok=mqWW0%2BEUb_4-_1Otnw@mail.gmail.com> References: <CAFHCsPX5kG_v-F-cjpyMQsT_b386eok=mqWW0%2BEUb_4-_1Otnw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/01/15 13:51, Svatopluk Kraus wrote: > Hi community, Hello, > I and Michal Meloun have done some work on ARM interrupt framework and > this is the result. > > We've started with intrng project with Ian's WIP changes, have looked > at Andrew's ARM64 git repository, and this is how we think an > interrupt framework should look like. We've implemented it with > removable interrupt controllers in mind (PCI world). It's not finished > from this point of view, however some functions are more complex > because of it. Is there any plan to make this framework generic across all the architectures? Some of our drivers as to create new interrupt controllers to handle event channel, it's an event notifications provided by Xen which is very similar to an interrupt (eoi/mask/unmask...). They are used by virtual devices in order to send/receive interrupts. The current code [1] already supports x86 which has a similar framework [2]. If your framework is used on all the architecture (especially ARM, ARM64 and x86), it would allow us to share the code between the architectures supported by Xen. Regards, [1] sys/x86/xen/xen_intr.c [2] sys/x86/x86/intr_machdep.c -- Julien Grall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54B94D71.90403>