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=-7.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 45B11C433DF for ; Tue, 4 Aug 2020 17:30:04 +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 15E33206C0 for ; Tue, 4 Aug 2020 17:30:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="v6buGJHj"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=ti.com header.i=@ti.com header.b="t9ierTec" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 15E33206C0 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=ti.com 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:Date:Message-ID:From: References:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=zoqD6q0qUTqJMthu3pWZCJZxx2qfUI7qtMAEdenQvJA=; b=v6buGJHjTPsxdDihyPJOSdpth qBdXmdWTDlr3lzro0n+cAiqlqxwhqEdDCpGdzEg8uDDYntNItcS+W593O18wnzb3D1JR08FLY12VY i5ba9pk/xtefLGpdlC7y8OKrcwAlFDvQpdhKNn1o0wbWyiNO9JAzPf1nr9Y68nfJT2Vxzi8CInbAZ QPxxYORm6eNg0u9HjxyUP2WqNNBFj9G/nm1O5RC4AQ29HY+OubCXRxWBw3tv73ZCoCsA5eez7uhu/ OIyFHLr7j2E0wxlnktmivxwksmnPG+v9O2jZOYJylSaOK6bBQdmxGWWUBf3XLO8VFolHtxZcHF808 0+KX5OmKw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k30k3-00026b-DV; Tue, 04 Aug 2020 17:28:47 +0000 Received: from fllv0015.ext.ti.com ([198.47.19.141]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k30k1-00025x-HL for linux-arm-kernel@lists.infradead.org; Tue, 04 Aug 2020 17:28:46 +0000 Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 074HSfvH020282; Tue, 4 Aug 2020 12:28:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1596562121; bh=OchtM4hMXabrchQB+CsAU+YXlIk3slpv/Gy19NRdCig=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=t9ierTecHRnH1J2s8r2c+Gm5WDg2bduNfqS+i88quz9shTz7pN7X5rjauI2TL/ez/ 3lnpoWOUXLQKBPqvrFC53YN4CsWyt0vZxxG1vpY3Fz/ryfo4Ma6PsMmzgS1VwgHh68 I15DD/b6S+yV2QUwaBaxV3isxB01Z1FgAqV0301k= Received: from DLEE113.ent.ti.com (dlee113.ent.ti.com [157.170.170.24]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTP id 074HSfK7003555; Tue, 4 Aug 2020 12:28:41 -0500 Received: from DLEE101.ent.ti.com (157.170.170.31) by DLEE113.ent.ti.com (157.170.170.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3; Tue, 4 Aug 2020 12:28:40 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE101.ent.ti.com (157.170.170.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3 via Frontend Transport; Tue, 4 Aug 2020 12:28:41 -0500 Received: from [10.24.69.198] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 074HSYwJ009910; Tue, 4 Aug 2020 12:28:37 -0500 Subject: Re: [PATCH v5 00/10] irqchip: ti, sci-intr/inta: Update the dt bindings to accept different interrupt parents To: Lokesh Vutla , Rob Herring , Suman Anna References: <20200728051735.6187-1-lokeshvutla@ti.com> <20200731181658.GA500828@bogus> <733bbcdc-8d29-51cc-f16e-7f95abb56ff2@ti.com> <20200731205953.GA774358@bogus> <051cd3d8-a52a-bdad-c4e8-7a05251fab33@ti.com> From: Sekhar Nori Message-ID: <74aee615-5dc4-20b2-293c-54a6b2768f73@ti.com> Date: Tue, 4 Aug 2020 22:58:34 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200804_132845_693265_2BE19AF2 X-CRM114-Status: GOOD ( 27.71 ) 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 , Marc Zyngier , 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 8/4/20 10:46 PM, Lokesh Vutla wrote: > Hi All, > > On 02/08/20 4:04 pm, Sekhar Nori wrote: >> On 8/1/20 2:29 AM, Rob Herring wrote: >>> 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... >> >> Looking at Bjorn's remoteproc tree[0], the common bindings patch is >> applied on top of other (unrelated) remoteproc patches, so merging it >> into Marc's tree is out of question unless Bjorn is willing to re-write >> his tree (probably not). >> >> The other option would be for Marc/Thomas to add these patches into a >> 'late' branch, to be sent to Linus after Bjorn's tree has been merged. >> Bjorn could help by sending his pull request early and someone from TI >> can keep an eye out for when its safe to merge. > > What can we do to take this forward? Once this series is merged, DT changes > should also be merged. Else DMA will be broken as DT backward compatibility is > broken. The DT parts should have been posted in the same series then, so as to not cause breakage after the series is applied, and to preserve bisect as much as possible. IMHO, the whole series needs to be merged together even if parts of it come from individual maintainers as immutable commits. Do the DT portions cause merge conflicts with what is already there in -next? I think the next step would be to post the series again, this time with DT changes included. Whether it goes into v5.9 or v5.10, thats probably needed anyway. Thanks, Sekhar _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel