Received: by 2002:a05:7412:8d11:b0:fa:4934:9f with SMTP id bj17csp573762rdb; Mon, 15 Jan 2024 06:45:53 -0800 (PST) X-Google-Smtp-Source: AGHT+IFeIigGGi28ApXwhR7QsBOCqCLuVffsgVpB9gn+Hu37UGj6lVtIQN5P4FXsFELzbpgLLrTx X-Received: by 2002:ac8:5b95:0:b0:429:fe77:281 with SMTP id a21-20020ac85b95000000b00429fe770281mr292302qta.56.1705329953159; Mon, 15 Jan 2024 06:45:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1705329953; cv=none; d=google.com; s=arc-20160816; b=SSp2JlqSQUJFbWeLn2WqR1yLe7d/KvT5ZJk0FpO0znhqq2kYRwFnzuYCqePJY4Rg79 Xgs66jkBigS27KJNgG9spL+Nnev+SVREfsRdSuk2atG3v5ZdwpBA50u2J+/w4XO4TLb1 QueYK2NramHseg/hlqzJ7XZj5m/VQWNrw8UFhfDu9AIjJcPTtyM9jU/Sx3101Jw9FADV KkTMwcpGlKn5szehz2knM77K5N6cgsjQCXhzgAYleCtl3nN0IvhRHkdiRA7mc0j5GmWC 4QNcu51GIHb6xvUAkYRlF5oy8kmM8gCn7DRnx0nX6DnnZNBWmkloSKwDehw8kzhuYbuT MDQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=tRLQ0Z88RKbDDHqezEjN3omnxCVQLyn4MWvS8yuJ5G4=; fh=mcnIo6+ZFRV/3PTYUnwvXzayGMNUZrbj9dIygjzUBFw=; b=rdF+AplExHBFNNcCe5qWSKQjy6KS7JNVDliBVK1Oj2We9gSMyDUtqcJkKhrsg1wB+O DXHiwDLow3wsAJO5uVKis3lhHrXQo4sELVkX+6wNSFJ8/86j3H9MvKeobao9nInxO5mT Nigtgpgs41fouk0LbdcqBsnNEYUkgQ70SMCt/1JrZisuhsYhVHNtYkllfpWhzy9RrBS8 f2tZwPKOW5kC9pwR2CBfoAAkkc3wzW2jKI/ud+Db28tYKkEsGb+H176Dn3Hl05vxxjuS sJrd7sWGntt92Lil6fyA1UT+U+SY4hOshoZ3yQoIIlVZRsNImDTCheiu+TPupzTOMcTt fE5w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="EQR/pEoz"; spf=pass (google.com: domain of linux-kernel+bounces-26122-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-26122-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id c1-20020ac87d81000000b00429ccb041f3si6513287qtd.45.2024.01.15.06.45.53 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 15 Jan 2024 06:45:53 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-26122-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="EQR/pEoz"; spf=pass (google.com: domain of linux-kernel+bounces-26122-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-26122-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id E6C921C21BC6 for ; Mon, 15 Jan 2024 14:45:52 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 59E3D175B7; Mon, 15 Jan 2024 14:45:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="EQR/pEoz" 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 6FFBD175A1; Mon, 15 Jan 2024 14:45:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 56BE3C433C7; Mon, 15 Jan 2024 14:45:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1705329940; bh=tRLQ0Z88RKbDDHqezEjN3omnxCVQLyn4MWvS8yuJ5G4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=EQR/pEozoncS5C3Ol7jiA/QacLXasDr5SzqDhp7hsq0JpO3tPfLz3ZVokJj8586el CjNNdgORcvFgXTBZXeHRrTEEv8OGN+DaWt4iql928ZOSZScnA79uc0Dl+x8Emf6vGn TGoB/lSOBEhLgpOhOv8bZ53DIdeAoNzHi9+oPgYgPpmOqEOmF+faeFG0k/N8ribQXk u+mpY34z54kgqNf6cg87CqtOhN3eBJSt3tqm2/UfuLDWOpobBRhIORmGyK6bJRCfM4 VO2BK8o28Uf6cfJjKB3GQymTLO0ISMdOEBNnXrcrXCH5A5DT+Qyv/uX/eTcsm87xdh etysZWABystcw== Date: Mon, 15 Jan 2024 15:45:37 +0100 From: Maxime Ripard To: "H. Nikolaus Schaller" Cc: Andrew Davis , Frank Binns , Donald Robson , Matt Coster , Adam Ford , Ivaylo Dimitrov , Maarten Lankhorst , Thomas Zimmermann , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , =?utf-8?Q?Beno=C3=AEt?= Cousson , Tony Lindgren , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Paul Cercueil , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-omap@vger.kernel.org, linux-mips@vger.kernel.org Subject: Re: Re: [PATCH RFC v2 04/11] ARM: dts: omap4: Add device tree entry for SGX GPU Message-ID: References: <20240108183302.255055-1-afd@ti.com> <20240108183302.255055-5-afd@ti.com> <122DC5ED-2AA7-46A0-845F-083922458385@goldelico.com> <7BC64F03-A4DF-411F-9B6F-6BCA436D9B50@goldelico.com> Precedence: bulk X-Mailing-List: linux-kernel@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="3xx7p3mwtk5a7dcv" Content-Disposition: inline In-Reply-To: <7BC64F03-A4DF-411F-9B6F-6BCA436D9B50@goldelico.com> --3xx7p3mwtk5a7dcv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 15, 2024 at 09:55:00AM +0100, H. Nikolaus Schaller wrote: > Hi, >=20 > > Am 15.01.2024 um 09:25 schrieb Maxime Ripard : > >=20 > > Hi, > >=20 > > On Fri, Jan 12, 2024 at 06:33:58PM +0100, H. Nikolaus Schaller wrote: > >>> Am 08.01.2024 um 19:32 schrieb Andrew Davis : > >>>=20 > >>> Add SGX GPU device entry to base OMAP4 dtsi file. > >>>=20 > >>> Signed-off-by: Andrew Davis > >>> --- > >>> arch/arm/boot/dts/ti/omap/omap4.dtsi | 9 +++++---- > >>> 1 file changed, 5 insertions(+), 4 deletions(-) > >>>=20 > >>> diff --git a/arch/arm/boot/dts/ti/omap/omap4.dtsi b/arch/arm/boot/dts= /ti/omap/omap4.dtsi > >>> index 2bbff9032be3e..559b2bfe4ca7c 100644 > >>> --- a/arch/arm/boot/dts/ti/omap/omap4.dtsi > >>> +++ b/arch/arm/boot/dts/ti/omap/omap4.dtsi > >>> @@ -501,10 +501,11 @@ sgx_module: target-module@56000000 { > >>> #size-cells =3D <1>; > >>> ranges =3D <0 0x56000000 0x2000000>; > >>>=20 > >>> - /* > >>> - * Closed source PowerVR driver, no child device > >>> - * binding or driver in mainline > >>> - */ > >>> + gpu@0 { > >>=20 > >> I wonder why we don't add a "gpu:" label here. > >>=20 > >> Almost all other subsystem nodes have one (e.g. emif:, aes:, dss:, dsi= :, hdmi:, etc.), > >> obviously for convenience when using a .dtsi file. > >>=20 > >> It would allow a board-specific DTS to easily add status =3D "disabled= " to avoid driver > >> probing or disabling the GPU (e.g. if there is no display). > >=20 > > There's no reason to disable it in the DT: the hardware block would > > still be there and it's rendering to memory so it still could be useful. >=20 > Well, if you know that the board does not have a dm3730 but a dm3725 with= out > GPU it is better to disable the GPU completely instead of loading the dri= ver > and make it detect by some internal bits that it has no GPU on the SoC. It shouldn't even be in the DTSI if it's not in the SoC. > > If there's no display on the board and you really don't want the GPU > > driver, then you can disable the driver or block the module loading, but > > it should be a distro / package / user decision, not a DT / kernel one > > still. >=20 > The same holds for aes: dss: dsi: hdmi: etc. If they are not used by some > board file, they don't change a single bit of the DTB [1] which IMHO would > be of reasonable concern to question additional labels. Not really, no. If there's no HDMI connector, the HDMI controller is useless. A GPU without a display can still be useful, depending on the workload. Maxime --3xx7p3mwtk5a7dcv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCZaVFEQAKCRDj7w1vZxhR xYLAAQD7hjmkBsOxfyoIsGNpz7ekssiiDTWUKJBEn79S9qdkjQD/ZF6T4o4JwKg2 1Y0Gk2k+BhScqbkykr/ZplBD8LyDcgg= =po+r -----END PGP SIGNATURE----- --3xx7p3mwtk5a7dcv--