Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2099028imu; Wed, 12 Dec 2018 09:27:15 -0800 (PST) X-Google-Smtp-Source: AFSGD/Ur5OGFlu1gbrMzR+eHQACz3zEDImVlmHgfop7v64amO4x6kLUIBq9Ut+fGkLVPIVIRzy7S X-Received: by 2002:a63:c24c:: with SMTP id l12mr19043500pgg.146.1544635635102; Wed, 12 Dec 2018 09:27:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544635635; cv=none; d=google.com; s=arc-20160816; b=gyBgeeFu9VCsQPlj/tY4ml8WOlhCc9Y48/50/3L7rmXW13kiXePKWkN9DOEMvb0O4P HQGIRqR3CskNkCxuKVE0d8fsw9yfEGHW0p01woa6Cdlzzm/oUVICjTM4D0QSCF9XwkMU byrR9sJz7PgkE7O+dis0wg2kmhWBISlnmlaOkCGihMpEU/3KotcCbDZeuqN5bJHvp5ml qq3zvOmInTiZEIK0J2IJobTypm3j/W3gXqpcgNYXIUzRNrt75xKbIrCiIQNx6EcmgRxz UIhzAc5tnFiWHcn44jwEVUWsoHI9yDVH0gMfKaLKPSXBQxt9n+awfM+mCcGrMQ0rWGXT ZSfQ== 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=qGAaXcGyF6+uqEQXUmv7VavHKjYiTOzbEkvMqtzdteM=; b=i6FvhkYwc0gL8qvW2OEScylWigsCgD+StOOiVZqD10UYuLTbVSua0n6hzuT+vhPKqZ NoHqCdgZG9S+IyvXKsFvLwlNl6fht0C/YmQgUKjiqjSHzyGtQbQ2Jmz6DIdOiZkz+u6j zbMwlyu+O7YSCRTdMxeESESGDbagsNB5uaiWW/4wMAxq6Cl9kXb6FpU7eTVFYFBggPQD 0UKCGMQq9aZ/lshoQaFjqRsc6IsV6R50YqNhNwZKk8WYixDJ+o+gM1gMg2Pi0c7frvRX 6YXn1QIwRtsvT/gcfTXzsYWpSzoeX32oQc7DS0tpTxQqmk+TI8/EXTaJyrAD+9lV1lkI NB4g== 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 37si14863502pgw.590.2018.12.12.09.26.59; Wed, 12 Dec 2018 09:27:15 -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 S1728006AbeLLR0A (ORCPT + 99 others); Wed, 12 Dec 2018 12:26:00 -0500 Received: from muru.com ([72.249.23.125]:57790 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726922AbeLLR0A (ORCPT ); Wed, 12 Dec 2018 12:26:00 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 4CF2F809F; Wed, 12 Dec 2018 17:26:02 +0000 (UTC) Date: Wed, 12 Dec 2018 09:25:55 -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: <20181212172555.GH6707@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> <20181126193332.GO53235@atomide.com> <5C112DB6.9090605@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5C112DB6.9090605@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 [181212 15:48]: > On 26/11/18 21:33, Tony Lindgren wrote: > >>> 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? > > > No. OK great. > > Also, is this maybe the same INTC that we already have a > > driver for in drivers/irqchip/irq-omap-intc.c? > > No, it is completely different. OK thanks for checking that. Regards, Tony