Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp336583imu; Mon, 26 Nov 2018 11:34:50 -0800 (PST) X-Google-Smtp-Source: AFSGD/WhftC616iRloow4q2rfVQcvQSAREAMFDAw8HRov+PeFIhqalTe90TeUYuQF9TV9+MofaWa X-Received: by 2002:a63:e516:: with SMTP id r22mr26617115pgh.256.1543260890609; Mon, 26 Nov 2018 11:34:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543260890; cv=none; d=google.com; s=arc-20160816; b=u6bpsvN+L5nXmJ7qZXj3BjsyxCdQGVsdcnpqF2CSPPT+m+ZrFtd8sELPQ9nGenC6Jf jnz71dxEkxJrmq6AN6AGMPHzkAv0yRHOWRqBufcu535j3SfGv2PNj/ws3a1iMvoo3LI3 H2rlnEfDi0N6QjDoTBsodt7rErZKN0eRcQQcr5nTIP2tgmrOiSqFAmQbEuHotNwjwRS5 s0qnllorBNwzDpOYXnb6VQtYjOarTtR5a5SjHBGziD8nCrgA90m3AsQ9O6mDNE0DmUkY HK4ShemPTfoL+i0kXbrdTPLH6jc1J1dMFCT6BzlEkjgHdSl3wC+LUoWilrtG8mk0CvWV OpLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=EUkmXJn5dcJB3Qv5N3NOgMaKzIgVGBtmJrSFE+hDuHs=; b=bhgRhfEsLUjSuQoMMabBwYe0TEXzKq8L40SEyTBP73U3qgv3IFwmISyy4I3Qi6l1yA QZY+BDY8dzmzoaUHjpE5HDguc4uGJ8GJ0wIxnkk9y6ToJ/I/PHA2x5V1v8K9bmQFhhpe 5xoTqgP2jqCE5A1IgMr3Q9oO1fubC1oWUdDa/f4daQnXX6mzr4YY0/HROJ8tUXu8Peyu 61Us/1DmMLZj/RPmmM11vxgEi4CXDN0aJvZblut68I7b7Dw2OLEqaRqHYZKwW2NkC9Du GArmr1kmqo6LHytX8N8RjAZfmihTM0PRY1Ip3XriRx0qfvN4guDhU+qngxKMHAXDzaMk Kp2Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p4si1243229pli.432.2018.11.26.11.34.15; Mon, 26 Nov 2018 11:34:50 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726516AbeK0G2o (ORCPT + 99 others); Tue, 27 Nov 2018 01:28:44 -0500 Received: from muru.com ([72.249.23.125]:55268 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726140AbeK0G2o (ORCPT ); Tue, 27 Nov 2018 01:28:44 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 5A9318068; Mon, 26 Nov 2018 19:33:37 +0000 (UTC) Date: Mon, 26 Nov 2018 11:33:32 -0800 From: Tony Lindgren To: Roger Quadros Cc: robh+dt@kernel.org, bcousson@baylibre.com, ssantosh@kernel.org, ohad@wizery.com, bjorn.andersson@linaro.org, s-anna@ti.com, nsekhar@ti.com, t-kristo@ti.com, nsaulnier@ti.com, jreeder@ti.com, m-karicheri2@ti.com, woods.technical@gmail.com, linux-omap@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH 08/17] soc: ti: pruss: Add a PRUSS irqchip driver for PRUSS interrupts Message-ID: <20181126193332.GO53235@atomide.com> References: <1542886753-17625-1-git-send-email-rogerq@ti.com> <1542886753-17625-9-git-send-email-rogerq@ti.com> <20181123163742.GC53235@atomide.com> <5BFBAA24.1070503@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5BFBAA24.1070503@ti.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Roger Quadros [181126 08:09]: > Tony, > > On 23/11/18 18:37, Tony Lindgren wrote: > > * Roger Quadros [181122 11:39]: > >> The PRUSS INTC module is reference counted during the interrupt > >> setup phase through the irqchip's irq_request_resources() and > >> irq_release_resources() ops. This restricts the module from being > >> removed as long as there are active interrupt users. > > > > So are there any reasons why this could not be just a regular > > drivers/irqchip driver nowadays? > > This is a reqular irqchip driver. Do you mean it should be moved > to drivers/irqchip directory? I think so, is there something preventing doing it? Also, is this maybe the same INTC that we already have a driver for in drivers/irqchip/irq-omap-intc.c? Regards, Tony