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 6C9EC20896A; Wed, 6 Nov 2024 18:30:47 +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=1730917847; cv=none; b=ipZ9vXTyEKQsChVL5I5No32t5YVZv2tu/phVCsrSikuF1S67CbvgMTsg+lCq2tG1HzvyXq+13gUI4zyjpv0D1BFR5aPFkaEYBifWMDUhj5JGhaWm6KPv+kfjfYMHyRYuD1ed1qycy93F0CVTkjWc7jQhOA0N5cPDook/4nFdZUo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730917847; c=relaxed/simple; bh=lwnwFqyElhS59Xfq7JeJ9Np9U8KffT4TejVqEqCOZp0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=SQ3wOJWJsod3o1yJujnBCK+7qsTArbo2HJ1X1lAWofH+CoVO1oeIkIwFwmf7lF+QmczI0ofxkcx+T9Mrg50HOy3xNM1bX3lwas3gys++9PYsV1W4njGuMuWrDNZlRIqtDv+dg0TLQ5xv2uOjGfOFba4ea2BBug/bDdVkB6F+EqQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Ncga7DDB; 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="Ncga7DDB" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9FF61C4CEC6; Wed, 6 Nov 2024 18:30:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1730917847; bh=lwnwFqyElhS59Xfq7JeJ9Np9U8KffT4TejVqEqCOZp0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Ncga7DDBTtU5oQZ5uy2fj4VeVQineuf963jbAweI5cQL8TstTDlhAj0dNYtVpHgT9 NjvMOiaYR8U0g+WtexhB47eFW1KxSqwXHprIWbQ+IThqovpgxFLCJq3bvaHXW0s0TH Nvi9g1U4hkfr7kVzo3/kIQYTaNqorVnhIn0+gzPIM1HaX5opU2d0i2AyDxEp0vYcWJ b3y/ndaOYgyNOiXTTHVfl/XquCmbuX9O7NV/LIAy0mb6t0sKa/Iq4Mg+Ux9O313/v/ MfLvBNHGtUsRCKaSgoyYbXtpA2w2fu/DIgkl+bfeEDipcHanKFXw7VCZ2tgCJ589bg uNfuvfK34/DkQ== Date: Wed, 6 Nov 2024 18:30:41 +0000 From: Conor Dooley To: Matt Coster Cc: Frank Binns , David Airlie , Simona Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , "dri-devel@lists.freedesktop.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Randolph Sapp , Darren Etheridge Subject: Re: [PATCH 04/21] dt-bindings: gpu: img: Allow dma-coherent Message-ID: <20241106-dried-spoils-f6ddd8020f40@spud> References: <20241105-sets-bxs-4-64-patch-v1-v1-0-4ed30e865892@imgtec.com> <20241105-sets-bxs-4-64-patch-v1-v1-4-4ed30e865892@imgtec.com> <20241105-linseed-steadfast-98cd8abe898c@spud> <5e26957f-dc79-42ef-a8a1-597fb386ae51@imgtec.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="f01tRNt2X5Z6+tQq" Content-Disposition: inline In-Reply-To: <5e26957f-dc79-42ef-a8a1-597fb386ae51@imgtec.com> --f01tRNt2X5Z6+tQq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 06, 2024 at 10:18:06AM +0000, Matt Coster wrote: > On 05/11/2024 18:06, Conor Dooley wrote: > > On Tue, Nov 05, 2024 at 03:58:10PM +0000, Matt Coster wrote: > >> This attribute will be required for the BXS-4-64 MC1 and will be enabl= ed in > >> the DTS for the TI k3-j721s2 in a subsequent patch; add it now so > >> dtbs_check doesn't complain later. > >=20 > > Sounds like the property should be made required for that integration. >=20 > This is something I went back and forth on. Where is the line drawn > between things that should be enforced in bindings and things that only > ever need to be specified once, so should just be left to the dt itself > to be the source of truth? >=20 > Having said that, I realise TI could spin a new SoC with a new dt but > use the same compatible string for the GPU; No they can't. New SoC, new compatible. > the "single" source of truth > then wouldn't be so single anymore. I guess by making this property > required for this compatible string, we're saying any use of it must > behave in exactly the same way, right? --f01tRNt2X5Z6+tQq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZyu10QAKCRB4tDGHoIJi 0oE5AP4yKMe2zZuHfZWRLLe1EVB1RY5SngwUhkXzFSPhIY8wLgEAlaS4WL2LzDDS 8YfEDzUHezrqSxoOdDYmEg7VZOPVXwQ= =AxQP -----END PGP SIGNATURE----- --f01tRNt2X5Z6+tQq--