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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 190E9C433EF for ; Wed, 9 Feb 2022 13:59:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234583AbiBIN7G (ORCPT ); Wed, 9 Feb 2022 08:59:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56464 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233068AbiBIN7E (ORCPT ); Wed, 9 Feb 2022 08:59:04 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E38E5C0613CA; Wed, 9 Feb 2022 05:59:02 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 76692B8219F; Wed, 9 Feb 2022 13:59:01 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 034D7C340E7; Wed, 9 Feb 2022 13:58:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1644415140; bh=sJkQVUoc2/03uklegtN+hrM5vjJewF0M3/NXHviuqmI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Syopwlp82ic3kwAeQKy+qsXtcjV8W7MVG1MoDIUwjD9l4ipwGR1thrRH76v2t3DE3 6Z3Mr2rq0Kg3XdjDREmcsVIkNuHWmCHGUBTFb1BWSOyGqk5LoLvSIrza/Kq3mMakMl WekrQxHSZCE9djwbXJRdWXxREfy3kx2zDAe5DD/ThK3U7aiuPVdDpp7KgXN03um03J e0VzTpw4dFMAe+KKz8eJ5P1/+ETGqKGhfscu/ZIQs2hikZWsDIcjB7g8h8uDY+4DH1 Hb0dYfn4Gy6L+USOaej9IOTfdqAZXkHUXphgbO80wBBFEPsDQYK6zF4dFBMYz5RARO qXjAAQzl/QKaw== Received: from sofa.misterjones.org ([185.219.108.64] helo=why.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nHnUn-006dYK-Um; Wed, 09 Feb 2022 13:58:58 +0000 Date: Wed, 09 Feb 2022 13:58:57 +0000 Message-ID: <874k585efy.wl-maz@kernel.org> From: Marc Zyngier To: Sander Vanheule Cc: Rob Herring , devicetree@vger.kernel.org, Thomas Gleixner , Birger Koblitz , Bert Vermeulen , John Crispin , linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 0/3] Per-parent domains for realtek-rtl IRQ driver In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: sander@svanheule.net, robh+dt@kernel.org, devicetree@vger.kernel.org, tglx@linutronix.de, mail@birger-koblitz.de, bert@biot.com, john@phrozen.org, linux-kernel@vger.kernel.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 06 Feb 2022 16:41:50 +0000, Sander Vanheule wrote: > > The original implementation for this interrupt controller/router used > an interrupt-map parser to determine which parent interrupts were > present. However, this controller is not transparent, so a list of > parent interrupts seems more appropriate, while also getting rid of the > assumed routing to parent interrupts. > > Additionally, N real cascaded interrupts are implemented, instead of > handling all input interrupts with one cascaded interrupt. Otherwise it > is possible that the priority of the parent interrupts is not respected. Just to be clear: this means that although you allow the new driver to somehow still work with the old DT, the opposite (old kernel, new DT) will probably fail horribly. Is everyone comfortable with that? M. -- Without deviation from the norm, progress is not possible.