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 54022C433F5 for ; Tue, 15 Feb 2022 12:09:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237496AbiBOMJg (ORCPT ); Tue, 15 Feb 2022 07:09:36 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:60736 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237465AbiBOMJc (ORCPT ); Tue, 15 Feb 2022 07:09:32 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0ABF1EF7AB; Tue, 15 Feb 2022 04:09:23 -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 AA8B4B817B9; Tue, 15 Feb 2022 12:09:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 660FEC340EB; Tue, 15 Feb 2022 12:09:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1644926960; bh=Ftj69RG3gmLoAWhVy5oxY9cQIuIItMQXxWGvo4VYRwY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=URnL3MBbK940bv95M5l+cUkuNwiIaEtbjmNO0xLsFMa6aFUPMptzT/WupeZ/fm/FX 1IL6NuPMN0bnKDV7WnMdxceoolfMV8NmA8eaF6zAtXrmaFEDte5mxLDb2hI07tCG/C H7ozX6A79BHaavhmEVyckzlLczIC2rWLhMfdqynkWCNyLx89V9jzgnYOJDhX8fmbzJ QbN5gIk+E8EniS/MSksbwGceADlpSpZHxM+3kDULkWFF8kQWZv2gCBEGRTwUkF9G6t 9EWXrKS2LDsGTeY3qjxaOClt5PSsQ1Zeyn/EuQWtv4aqkr328BOU69urbzN+yj6QdJ zSReuJ86//sgw== 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 1nJwdy-0082gW-FU; Tue, 15 Feb 2022 12:09:18 +0000 Date: Tue, 15 Feb 2022 12:09:18 +0000 Message-ID: <87czjo49ht.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 v5 0/4] 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 Mon, 14 Feb 2022 18:56:57 +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. My original question[1] still stands. An old kernel breaks with a new DT. I am not convinced that this is an acceptable outcome. M. [1] https://lore.kernel.org/all/874k585efy.wl-maz@kernel.org -- Without deviation from the norm, progress is not possible.