From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Subject: remoteproc: Resource table for IRQs Date: Tue, 13 Mar 2012 10:41:43 +0100 Message-ID: <4F5F1657.9090200@monstr.eu> Reply-To: monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Ohad Ben-Cohen Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, LKML , John Williams List-Id: devicetree@vger.kernel.org Hi Ohad and others, I would like to open new topic about remoteproc and IRQ. As you know we run AMP on dual core arm cortex A9. The first cpu runs Linux and the second rtos. Both cpus use the same GIC and Linux is able to forward IRQ to specific CPU. Currently this functionality is hardcoded and the kernel always forward specific IRQs to firmware. I think that will be good to move IRQ description to resource table and kernel could check if this IRQ is used or not and if not then setup GIC to forward this IRQ to the second CPU. I think that reasonable solution is to extend fw_resource_type for RSC_IRQ. What do you think? Thanks, Michal -- Michal Simek, Ing. (M.Eng) w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/ Microblaze U-BOOT custodian