Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752389AbbKYSW4 (ORCPT ); Wed, 25 Nov 2015 13:22:56 -0500 Received: from exsmtp01.microchip.com ([198.175.253.37]:52350 "EHLO email.microchip.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750914AbbKYSWq (ORCPT ); Wed, 25 Nov 2015 13:22:46 -0500 Subject: Re: [PATCH 02/14] irqchip: irq-pic32-evic: Add support for PIC32 interrupt controller To: Marc Zyngier References: <1448065205-15762-1-git-send-email-joshua.henderson@microchip.com> <1448065205-15762-3-git-send-email-joshua.henderson@microchip.com> <20151122114530.10bca210@arm.com> CC: , , Cristian Birsan , Thomas Gleixner , Jason Cooper From: Joshua Henderson Message-ID: <5655FC74.9090204@microchip.com> Date: Wed, 25 Nov 2015 11:22:44 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151122114530.10bca210@arm.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1545 Lines: 44 On 11/22/2015 4:45 AM, Marc Zyngier wrote: > On Fri, 20 Nov 2015 17:17:14 -0700 > Joshua Henderson wrote: > > Joshua, Cristian, > >> From: Cristian Birsan >> >> This adds support for the EVIC present on a PIC32MZDA. >> >> The following features are supported: >> - DT properties for EVIC and for devices that use interrupt lines >> - persistent and non-persistent interrupt handling >> - Priority, sub-priority and polariy settings for each interrupt line >> - irqdomain support >> > > I haven't reviewed the code yet, but the fact that you allow (and > actually request) the interrupt priorities to be encoded in the DT > raises some concerns: > > - Aren't priorities entirely under software control (and hence don't > belong in DT)? These are hardware priorities configured by software. They arbitrate pending hardware interrupts to the CPU. We can agree that DT is probably not the best place for this configuration. They will be removed from the binding. > - More crucially, how do you deal with nested interrupts when you have > interrupts running at different priorities? Most parts of Linux > cannot cope with that without additional support. > We do not support nested interrupts. > Thanks, > > M. > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/