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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8BE98C5320E for ; Thu, 22 Aug 2024 09:46:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=qfCsE2TARh/0Jkqs1tOSCtPuFozHgbbnBIGeahfVo4w=; b=WhL3IfV352lkFX92ei/5ADTWVZ GgZ8PN1rYz1Y1C1uYIAIyZVU0Q4pKLsH1S2dRCuCmUxhTmU4vyrNYs0P7924AYPuS4+mOH305qGnQ lJ8j+XoqDA0LC5wq4nWvJG54tH0TmiF9jyAEkg3LzVQpoO6S3OiWHAauL1R4PWyZ0/tLNQJWRUB3X 1oCKpoJ1CxBTwhA1AyqlUzOTtYz79Vl+/vOEqWVJJx6KnIuAyurEJW7yIP1sG8FnShSClg9mwB4T/ dkyuSUTNFkLVLFS7kgdQSeyOrfqZcyhwyFsitTUJexOZA5Bv+n/luBZ1aHQ4h3sHNB7oAl05RSXO7 P2NkNBYQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sh4OB-0000000CJ7i-2GD6; Thu, 22 Aug 2024 09:45:55 +0000 Received: from nyc.source.kernel.org ([147.75.193.91]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sh3Nf-0000000C6XQ-1Zza; Thu, 22 Aug 2024 08:41:30 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id 64404A40136; Thu, 22 Aug 2024 08:41:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9AA19C4AF09; Thu, 22 Aug 2024 08:41:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1724316077; bh=qfCsE2TARh/0Jkqs1tOSCtPuFozHgbbnBIGeahfVo4w=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ImlOSxZqPU2Q0pU6PiB1Lrd06gaA6GAh3l9ygooynVI9lp1GJn398Le0w3DFW2Dc4 beVWkktTt4Ktr+VfuPtaDtr0xhQJq7Q/ImOyeTHo+bWYI9R/TQhkaoDL+3Fm7C+qKP QyaX1MbnL1XzNmNx5fXaQI2L5vdYywsXzOTQJ3hf0SCp4Xp9tJfercshJir8dD0SmA Lc8RIj1kG3pg7b7crOFi8GCrlgGQ6Pp23KsGG1NqIk8BYibZ1ySXDAWTbRz3cKLwOj saAUZAyKd4AlPGd42RImlnWsxCSX/t7IBSzfRlgRprdFs2UEfrKb2YWCVHrV27OVMU dNIoNoGWLm/0Q== Date: Thu, 22 Aug 2024 09:41:10 +0100 From: Conor Dooley To: Heiko =?iso-8859-1?Q?St=FCbner?= Cc: Cristian Ciocaltea , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Daniel Vetter , Sandy Huang , Andy Yan , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Mark Yao , Sascha Hauer , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org, kernel@collabora.com, Alexandre ARNOUD , Luis de Arquer Subject: Re: [PATCH v4 3/4] dt-bindings: display: rockchip: Add schema for RK3588 HDMI TX Controller Message-ID: <20240822-pushchair-premises-f4055779216a@spud> References: <20240819-b4-rk3588-bridge-upstream-v4-0-6417c72a2749@collabora.com> <7E8109D4-A353-4FE3-9152-3C3C6CB7D634@sntech.de> <2085e998-a453-4893-9e80-3be68b0fb13d@collabora.com> <4167579.6PsWsQAL7t@diego> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Z+weBBqJ58Bi1CtB" Content-Disposition: inline In-Reply-To: <4167579.6PsWsQAL7t@diego> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240822_014119_795439_2FD6FDBF X-CRM114-Status: GOOD ( 14.29 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org --Z+weBBqJ58Bi1CtB Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 22, 2024 at 09:01:34AM +0200, Heiko St=FCbner wrote: > @Conor: just for me, did some shift happen in our understanding of dt- > best-practices in terms of syscon via phandle vs. syscon via compatible? >=20 > Because Rockchip boards are referencing their GRFs via phandes forever > but similar to the soc vs non-soc node thing, I'd like to stay on top of > best-practices ;-) If IP blocks, and thus drivers, are going to be reused between devices, using the phandles makes sense given that it is unlikely that syscon nodes can make use of fallback compatibles due to bits within that "glue" changing between devices. It also makes sense when there are multiple instances of an IP on the device, which need to use different syscons. My goal is to ask people why they are using these type of syscons phandle properties, cos often they are not required at all - for example with clocks where you effectively need a whole new driver for every single soc and having a phandle property buys you nothing. --Z+weBBqJ58Bi1CtB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZsb5pgAKCRB4tDGHoIJi 0rLhAQDqY1gu1PD4V30d8emILN4UQA7IqbfNHPYXVGBNqADBXwEAj497+bHi0qU5 bnjxze+ZiZvdByZ4C9o+h+n3wfVJhQA= =vu81 -----END PGP SIGNATURE----- --Z+weBBqJ58Bi1CtB--