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 379FCC433EF for ; Thu, 6 Jan 2022 17:31:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241861AbiAFRbn (ORCPT ); Thu, 6 Jan 2022 12:31:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241811AbiAFRbk (ORCPT ); Thu, 6 Jan 2022 12:31:40 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4D2A9C061245; Thu, 6 Jan 2022 09:31:40 -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 dfw.source.kernel.org (Postfix) with ESMTPS id D41C961D3C; Thu, 6 Jan 2022 17:31:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2E81EC36AEB; Thu, 6 Jan 2022 17:31:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1641490299; bh=Vpb/tleuQ8bUWlWWTmuzP4ZG+naSurYxE7Y2VV6VqbM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=L37roIGYDMmD7/iXbXDXZ5aa5f6f0u+i+mneCsC/UqA5yPIjeofvrFXGcXRY3SsTm PnA60uOdQsCbcX3QDpmlnM2R7vYqwRi07rFotkZrXm78LBFKonA7/V3N8hzXB1Nx9e P98K0+LH6LdugozkKlWheSZ4CYvZD+52CtsZBM+M6BK1CuDkmDTAw5YyHQRrelJfwY gNd4AyBLCqh1MzVX5SLMxBS59qzJmh3VeWfn5s5Ns2H0sxrZKFC9N0eYb57ocxgmnM iu09pN0RWEQmvUwArk2gQ7aEYL8SFS5P4Mkc5GpSnFg6kPmidbXG11zPS06HnOslxn DGJGUxU7UZ2Lg== 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 1n5Wbx-00GOhn-A0; Thu, 06 Jan 2022 17:31:37 +0000 Date: Thu, 06 Jan 2022 17:31:36 +0000 Message-ID: <874k6gvkhz.wl-maz@kernel.org> From: Marc Zyngier To: Marek =?UTF-8?B?QmVow7pu?= Cc: Pali =?UTF-8?B?Um9ow6Fy?= , Lorenzo Pieralisi , Bjorn Helgaas , Rob Herring , Thomas Petazzoni , Krzysztof =?UTF-8?B?V2lsY3p5xYRza2k=?= , Russell King , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 10/11] PCI: mvebu: Implement support for legacy INTx interrupts In-Reply-To: <20220106182044.3ff0828c@thinkpad> References: <20220105150239.9628-1-pali@kernel.org> <20220105150239.9628-11-pali@kernel.org> <87bl0ovq7f.wl-maz@kernel.org> <20220106154447.aie6taiuvav5wu6y@pali> <878rvsvoyo.wl-maz@kernel.org> <20220106162047.vqykmygs75eimfgy@pali> <877dbcvngf.wl-maz@kernel.org> <20220106182044.3ff0828c@thinkpad> 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=UTF-8 Content-Transfer-Encoding: quoted-printable X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: kabel@kernel.org, pali@kernel.org, lorenzo.pieralisi@arm.com, bhelgaas@google.com, robh+dt@kernel.org, thomas.petazzoni@bootlin.com, kw@linux.com, rmk+kernel@armlinux.org.uk, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.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 Thu, 06 Jan 2022 17:20:44 +0000, Marek Beh=C3=BAn wrote: >=20 > On Thu, 06 Jan 2022 16:27:44 +0000 > Marc Zyngier wrote: > > You are completely missing my point. I'm talking about data > > structures, you're talking about interrupts. You have this: > >=20 > > struct mvebu_pcie_port { > > // Tons of stuff > > struct irq_chip intx_chip; > > }; > >=20 > > What I want you to do is: > >=20 > > struct mvebu_pcie_port { > > // Tons of stuff > > }; > >=20 > > static struct irq_chip intx_chip =3D { > > .name =3D "INTx", > > .irq_mask =3D mvebu_pcie_intx_irq_mask, > > .irq_unmask =3D mvebu_pcie_intx_irq_unmask; > > }; > >=20 > > That's it. No more, no less. > >=20 > > M. > >=20 >=20 > Hmm, but struct irq_chip contains a dynamic member, > struct device *parent_device; > Isn't that used? Or are you planning to kill it? Indeed, and I am definitely planning to kill it. This is the wrong place for this stuff, and I want it gone. There are thankfully very few users of this misfeature. M. --=20 Without deviation from the norm, progress is not possible.