From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9359FC433E0 for ; Fri, 31 Jul 2020 21:01:41 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 5F7E9208E4 for ; Fri, 31 Jul 2020 21:01:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="g5SlsE8K" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5F7E9208E4 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=I0WpcYQNKG/qxpst++amWdtFvvRWtcFals4hA4H9soo=; b=g5SlsE8KV8yHIWVUok7tj/HHE vQotzkBIVuOfcTOJlkhqxwLTtyBX5h4CHp+j+BHIgPdTELnbL/hZ6QXVs/WRUWx3nPtzDWA8nv/MR rM3DkakYn1AnyaaJWFJj/4efAuN9n6f5kZKp0Rf+0M+AFDXJ64ESNmr45CUKacipcuRRE1VmwR0XU xLBdr73gOjQSJayVANEqAAASRucre3MwTPmNKBDaYjfHKAtWWB8HjCur7ZLnqDmEk9QGTpgMwFqtD n60sKg1dqg6A2konZjELwfGq07iueAdnjDMh/6nPUXyYxz6aeO6A0QjaNIOLMtz3awj8C+TFj5WRj Rk1wgWfZg==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k1c8E-0005T8-4Y; Fri, 31 Jul 2020 20:59:58 +0000 Received: from mail-il1-f196.google.com ([209.85.166.196]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k1c8B-0005Sf-Ma for linux-arm-kernel@lists.infradead.org; Fri, 31 Jul 2020 20:59:56 +0000 Received: by mail-il1-f196.google.com with SMTP id z3so16230460ilh.3 for ; Fri, 31 Jul 2020 13:59:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=UYcNl03XooJ83wKwVlukk4UGjBfn5KW8QexrmJDVD10=; b=M/H86Mx3mRhOs23FNTA544yJd89byC/lPoYOcp7gaBdow7uc/FqXKS0oXgupfLh8cf t2YYvL4rV3Lc3MiqDaQM5/LHeqaxhN9k+EXwH2YFjmXlVFMpplit42RftTDU7uyQyoT8 HmkNJckh2CP7mtUJgFgepJ7jInDITuhKKSfiZzTRz+iLzbO7REx7tHjlTuTqD18IdhLZ oMPcY5oUzpO3haWVGJkRaiQRcqgFwtvJxVgowGeKOsfmQRLHIqgSfMeJ3TrCEYGCPLG/ kJuHLvV1o+XdqC9U24YuJ/xnYh3ptkA3uIyp0wYPMisi/iC2bUcdOOb97YUk78RuPnzL ZkYg== X-Gm-Message-State: AOAM530daSqJVH8mVZ3HPmhslO4jl194lUF2dPYMim5mdG923bmY8ynJ MbAzgeIcHycg7sKgA2StAQ== X-Google-Smtp-Source: ABdhPJykewMkcC30Hs0+WIUeNisNnIjDwBGDQGvpjdW/aPLEpKXE99/aKWnPBIH3NtLFO/eDZ/rg9w== X-Received: by 2002:a92:dc90:: with SMTP id c16mr5589222iln.202.1596229195088; Fri, 31 Jul 2020 13:59:55 -0700 (PDT) Received: from xps15 ([64.188.179.252]) by smtp.gmail.com with ESMTPSA id r12sm4916466iol.5.2020.07.31.13.59.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 31 Jul 2020 13:59:54 -0700 (PDT) Received: (nullmailer pid 776977 invoked by uid 1000); Fri, 31 Jul 2020 20:59:53 -0000 Date: Fri, 31 Jul 2020 14:59:53 -0600 From: Rob Herring To: Suman Anna Subject: Re: [PATCH v5 00/10] irqchip: ti, sci-intr/inta: Update the dt bindings to accept different interrupt parents Message-ID: <20200731205953.GA774358@bogus> References: <20200728051735.6187-1-lokeshvutla@ti.com> <20200731181658.GA500828@bogus> <733bbcdc-8d29-51cc-f16e-7f95abb56ff2@ti.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <733bbcdc-8d29-51cc-f16e-7f95abb56ff2@ti.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200731_165955_775963_9B56C046 X-CRM114-Status: GOOD ( 24.70 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Nishanth Menon , Peter Ujfalusi , Grygorii Strashko , Device Tree Mailing List , Lokesh Vutla , Marc Zyngier , Sekhar Nori , Bjorn Andersson , Tero Kristo , Santosh Shilimkar , Thomas Gleixner , Linux ARM Mailing List Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Jul 31, 2020 at 01:24:17PM -0500, Suman Anna wrote: > On 7/31/20 1:16 PM, Rob Herring wrote: > > On Fri, Jul 31, 2020 at 06:01:50PM +0100, Marc Zyngier wrote: > > > On 2020-07-28 06:17, Lokesh Vutla wrote: > > > > Hi Marc, > > > > This is continuation of the RFC patches[0] regarding the driver > > > > updates to support for following interrupt parent connection: > > > > - INTR -> INTR > > > > - INTA -> GICv3 > > > > The current existing driver assumes that INTR is always connected to > > > > GICv3 and INTA is always connected to INTR. > > > > > > I'm OK to take this if I can get an Ack from RobH on the three > > > DT patches that still need it. > > > > Reviewed-by: Rob Herring > > > > However, there's a dependency on > > bindings/arm/keystone/ti,k3-sci-common.yaml. > > > > That's a dependency on this being merged. I don't care if it breaks in > > your tree, but I care for -next and Linus' tree. There could also be > > other 'make dt_bindings_check' failures/warnings with this as the above > > dependency prevents further testing. > > > > Bjorn did pick up the above common binding file through the remoteproc tree, > and it is available in -next. That said, I donno the merge order between > remoteproc and irq subsystem trees into -next, and if that is a concern. I'm less concerned about merge order at this point. -rc1 not being broken is the low bar I have... Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel