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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7D65DC433F5 for ; Wed, 16 Feb 2022 14:11:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232503AbiBPOLo (ORCPT ); Wed, 16 Feb 2022 09:11:44 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:39470 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233931AbiBPOLn (ORCPT ); Wed, 16 Feb 2022 09:11:43 -0500 Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2C8B163F2; Wed, 16 Feb 2022 06:11:29 -0800 (PST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id 48E4D580790; Wed, 16 Feb 2022 09:11:29 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 16 Feb 2022 09:11:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cerno.tech; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm2; bh=i2qG2nO4rS4VmdzOeglqVq9vsAN10ZORWEZaYZ TfUK8=; b=pSrwM38yuMw01iuenrss84p89r/K8SzJ/EPX2kdCW/uKq44b3bFEk2 ne/VfaKSDxLaMY5X8TQduLAycXwsvJG0gcNdql9jYIAOOSWT7PWyyvmZKHVz3/+w ovDxvwgag/EV6e2ZBBCHFgaVcSjjGddXk7yJckRxktRKl4ABa1J4Wo0F3AtdNt5o JU3BqE+2FZ0lYPCRhlUigozQTfr1yBvRTbJusknLN93XC626NHwM8Hw28Q9+d7go rxeADLhY+bJ9Bk/KBOtoiS/PiowmnpM4uD+Hezp74IKtEEZfsIoZ8qM5h96fN/Ty fC850dzW6mf8tfsa2rQtuIz6/MSAIxXA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=i2qG2nO4rS4VmdzOe glqVq9vsAN10ZORWEZaYZTfUK8=; b=ihcbqs4iq5kxd5MoQKrvNwO5Ov2/WjbOI Y/4CGWIOC49uLE71AN3EDNOHEbEPEo1Afec80qmZms6Qiby6amGxcisqyaLSOymb AG2o7qI+oMW+Y9Ru2rVZ+yyCn4MDoIThv+pAGY7R6dknG1lZTO8pLCV53aOCtbgo vfuyMhsat9TS8u7I2Ma5f8lfvtNXQCNX9xnHZ08XgcBKTckVVOd48YFBVre3asBc jRZXpDvQQfGC84uRno1oryfNvLc8D4tGiRnB0AqHIjZES/JvXE/ZEAFNV1VW/eXh TGmZUVCfBrt4NEbo1AzMfzjnIf84kTJLLqvrVibaJEaGiED85E8WA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrjeeigdehlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofgrgihimhgv ucftihhprghrugcuoehmrgigihhmvgestggvrhhnohdrthgvtghhqeenucggtffrrghtth gvrhhnpeelkeeghefhuddtleejgfeljeffheffgfeijefhgfeufefhtdevteegheeiheeg udenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmrg igihhmvgestggvrhhnohdrthgvtghh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 16 Feb 2022 09:11:28 -0500 (EST) Date: Wed, 16 Feb 2022 15:11:27 +0100 From: Maxime Ripard To: Sui Jingfeng <15330273260@189.cn> Cc: Dan Carpenter , Lucas Stach , Maarten Lankhorst , Roland Scheidegger , Zack Rusin , Christian Gmeiner , David Airlie , Daniel Vetter , Rob Herring , Thomas Bogendoerfer , Krzysztof Kozlowski , Andrey Zhizhikin , Sam Ravnborg , suijingfeng , linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Randy Dunlap Subject: Re: [PATCH v6 1/3] drm/lsdc: add drm driver for loongson display controller Message-ID: <20220216141127.2b7frii62w7xp3tu@houat> References: <20220203082546.3099-1-15330273260@189.cn> <20220203082546.3099-2-15330273260@189.cn> <20220203085851.yqstkfgt4dz7rcnw@houat> <11ac5696-29e3-fefa-31c0-b7b86c88bbdc@189.cn> <20220209084908.kub4bs64rzhvpvon@houat> <84bfb2fc-595c-3bae-e8a0-c19ccbcfcfd8@189.cn> <20220209161624.42ijbnhanaaari46@houat> <965ca520-229f-5729-bf06-ae64ed3af383@189.cn> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="if4dkzifithtnd47" Content-Disposition: inline In-Reply-To: <965ca520-229f-5729-bf06-ae64ed3af383@189.cn> Precedence: bulk List-ID: X-Mailing-List: linux-mips@vger.kernel.org --if4dkzifithtnd47 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 16, 2022 at 09:34:47PM +0800, Sui Jingfeng wrote: > On 2022/2/10 00:16, Maxime Ripard wrote: > > And, to reinstate, we already have a mechanism to set an EDID, and if it > > wasn't an option, the DT is not the place to store an EDID blob. >=20 > Hi, >=20 >=20 > if DT is not the place to store EDID blob, why nvidia can do that ? >=20 > output->edid =3D of_get_property(output->of_node, "nvidia,edid", &size); > [1][2] Because that binding is 10 years old and never got reviewed by a DT maintai= ner. Things change, some things we did in the past have been mistakes that we don't want to repeat, can we move forward? Maxime --if4dkzifithtnd47 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCYg0GDwAKCRDj7w1vZxhR xfrUAQDoc1GrrZYHXc7NMWEIsyPQ1lsWTu8qjcZQon9X0OfsPgEAwkVb2Uv/vcHy dC/YeqCI6cZBcH7PZOIyLedrztqdEgA= =ryuu -----END PGP SIGNATURE----- --if4dkzifithtnd47--