From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 119AD13957E; Mon, 26 Jan 2026 20:00:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769457641; cv=none; b=Ug3NZPxb3YsrIrRAhg4CiHfI/faKYOjs+2D2D6P/bQrIxyNueY+XKh1AjjvZ4UEMwsZGDh2WJpekotngm2lGxt7uFBwESWyNM9mtQ4mshYbCAh59ASO7B79YW1gCF6/S6iozW8vBb6W7+gx9AK7E3Hqaozu2zojt1/YIl1yQjNE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769457641; c=relaxed/simple; bh=W/s9B8G5AAVa1Ka8hwUbZ0G6I72DbzHIqE5HpGQCPNk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Dj2t5pGCEMF7AXzx/CpG7ZORiLENbS0GY7gupcYXafUNkZibqq9WCVA9dLL4S+XGeAIItUaxzo+sr/1g5RulNLw/643OeIBO8mJGYr0DSI/we+u47AK72NkLIawKDoNZB5tXy6IJy2kQUX8cO3E9lHx3OnM+9vXSj8/OTlYqtyQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=vQpeICey; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="vQpeICey" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 489E6C116C6; Mon, 26 Jan 2026 20:00:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1769457640; bh=W/s9B8G5AAVa1Ka8hwUbZ0G6I72DbzHIqE5HpGQCPNk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vQpeICeyJSjkOhlUCdhsHfBjOVMQbxJZt5iv694GjcLRSgCdNa70WSlPLusbcNSIG cf7KBZEUGxL7QkUkQmqPRUFfGjPUxIu2D2ugRxPTcbsnbB9AN3a7LhW/vJL0M0n2Ki L5w0znY9rQ5iBzW9JnwxwmEynbt7Hl8LnZ2YNbpywE7BVbGpt1Or/HrmpshUPduDm6 OKoBYCLyyvrtN0n25eTeS+/3E84PyvcO1me1ZMeo99FNFowVq2CWwoGlKmj/VEVwYm gno+nZ5oYW8my4Lrun/5mweiK8UP4tn92qiPzifhiby96RbUkuic0livRkinilnaxf DKj7WQMGi/IBQ== Date: Mon, 26 Jan 2026 20:00:33 +0000 From: Conor Dooley To: Jan Petrous Cc: Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Maxime Coquelin , Alexandre Torgue , Chester Lin , Matthias Brugger , Ghennadi Procopciuc , NXP S32 Linux Team , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Rob Herring , Krzysztof Kozlowski , Conor Dooley , netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, imx@lists.linux.dev, devicetree@vger.kernel.org Subject: Re: [PATCH v3 2/4] dt-bindings: net: nxp,s32-dwmac: Declare per-queue interrupts Message-ID: <20260126-blinker-secluding-a745f60caccb@spud> References: <20260123-dwmac_multi_irq-v3-0-cc53f2be8961@oss.nxp.com> <20260123-dwmac_multi_irq-v3-2-cc53f2be8961@oss.nxp.com> <20260123-dinner-aloft-e57deb6c546a@spud> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yK1i+yQq5ZBwutQC" Content-Disposition: inline In-Reply-To: --yK1i+yQq5ZBwutQC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 26, 2026 at 01:46:45PM +0100, Jan Petrous wrote: > On Fri, Jan 23, 2026 at 05:13:03PM +0000, Conor Dooley wrote: > > On Fri, Jan 23, 2026 at 11:09:55AM +0100, Jan Petrous via B4 Relay wrot= e: > > > From: "Jan Petrous (OSS)" > > >=20 > > > The DWMAC IP on NXP S32G/R SoCs has connected queue-based IRQ lines, > > > set them to allow using Multi-IRQ mode when supported. > >=20 > > The binding only supports s32{g,r} devices, why is the existing minimum > > retained? What devices are going to not have all 11 interrupts > > connected? > >=20 >=20 > The original idea was to support backward compatibility, as older DTs > didn't contain queue-based interrupt lines described. >=20 > But now, when you asked, I started to think it is not needed, > the requirement for backward compatibility is managed inside the driver > and yaml shall describe the hardware not used configuration. Just to be clear, cos the last portion of that "yaml shall..." isn't to me, you mean that the driver will support 1 or 11 interrupts but you will make the binding only allow 11? That would be fine. Just note in the commit message that all of these devices have the 11 interrupts. > Is it my understanding right? Should I provide v4 with minimum =3D 11? --yK1i+yQq5ZBwutQC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCaXfH4QAKCRB4tDGHoIJi 0tNuAPoDxV/IAeHe/4sVvqAaVI5emQP++yc9VFODMCulOLOD3wD/ZLyJy71N+Tg4 4efjJ30p/XNWBZVQgvn0cruDyAqP1ws= =0Jjo -----END PGP SIGNATURE----- --yK1i+yQq5ZBwutQC--