Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp2019402pxb; Wed, 9 Feb 2022 09:12:14 -0800 (PST) X-Google-Smtp-Source: ABdhPJy8x98pLSUqFH0BBlz0Sxp2iB1pskomtxQckaH1LBoncYjMeP7Du/LRAaN3ZEWIwGtxZ0Ey X-Received: by 2002:a17:907:e9f:: with SMTP id ho31mr2911661ejc.646.1644426734198; Wed, 09 Feb 2022 09:12:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644426734; cv=none; d=google.com; s=arc-20160816; b=zR5Bz+xX2TGTjYG9FRuxoVAHaFxyQ4RSLFRye/Imuv/LKX0Rlxa5TCY6L3TEnO/yJh aGCzOV8xsN3zDKZZvW5Xpwosoo283Z5T6CXyinF98RKY+cGjCLDH4pMqsUxmpUTRW0rQ TGDly4bI8v2r0q3qmCNARBOYvrizEqNNa61iB6Iez3NobsqgK4Y+ttcZokoVwzQqlxKy kECHgvftIGtOFmpA68KpTm6cSEFLeljn48HB+cBsQ8bpTx73id9jH7OBuV8C9zwSPvt1 cEyN3vLwUiX8ZkOieihsbAVZrIMO7XJA3xeY5hr19HmJ1qHo0bpUzycgQNpFsVOtbMPF xD0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=6C3Zbv7qcftcJPNdinXDELfCRJAPbtGEO9aofqELC1c=; b=ICT3xQASV/EugZ86GxHDdgDuqwOOZG2zJJ/ZTNU6pMRkQOw0gS5EDfJ4t83tyUem9J hshrdmPDwrrJC3coIfk5hqfzjA2L4m9vZB9lqgc3l956RjKDi3yKslo6ZJeCpttbFM8z URKcQwdJQoBgRXdq9Jxh4VPw4FK+dQnRxe5OXj6FuCDo3oec1111qK3n32w1gEMrtCg+ rPUJA/BKHbzDbQwuDIU4UOpxLhTOUqAfPsiU9LqQzT0jDC+DEXIuHvR28EMM/L2L+0Sg iK7YD0jdGYj0r3mOB6a3iKJ1Akx5ckXP49k2BcQrG4nNHdGWQwPogQMwU2Z2L6UiFXPy g7Vw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@cerno.tech header.s=fm2 header.b=RbTJLLPS; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=juG876Jt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=cerno.tech Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id sb12si4881442ejc.776.2022.02.09.09.11.46; Wed, 09 Feb 2022 09:12:14 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@cerno.tech header.s=fm2 header.b=RbTJLLPS; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=juG876Jt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=cerno.tech Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234722AbiBIOEk (ORCPT + 99 others); Wed, 9 Feb 2022 09:04:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34554 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231210AbiBIOEj (ORCPT ); Wed, 9 Feb 2022 09:04:39 -0500 Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8A7ACC0613C9; Wed, 9 Feb 2022 06:04:39 -0800 (PST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 0A9AD5801A9; Wed, 9 Feb 2022 09:04:37 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 09 Feb 2022 09:04:37 -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=6C3Zbv7qcftcJPNdinXDELfCRJAPbtGEO9aofq ELC1c=; b=RbTJLLPSHVAvRbZaSx+PE/OOh6dwrdKo5fF8ddis1mPVVlOd+rbbOw WNgNng9NOAg2tC7ME61PAATrqcEL2Iq1EhU+dNttV2/alXDEY+TRmrxgSI4qQ6Q2 gxdOFwVQgGTzVPWATM+X56Yfwqf/G/QqaTq5zIVe0XGUQaXIhYmh9RhVa+4gR9wR cJMYUz0oxESU6HCz0r3DP7Q0h01iiI2FqG9xPc+CPwpN54Wajx7WXuQWFGAjozhZ ItVHbeQ1H7j61Ph7OLb8cTuWMxdQDOyKAwRTHLNd+4MA7xfpA0zEl6cibfdfo2o1 g8FvQ8oaj8urf9tG307CeqSKVDoQsFng== 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=6C3Zbv7qcftcJPNdi nXDELfCRJAPbtGEO9aofqELC1c=; b=juG876JtEkhqls5pvMUbR4O2Cp+hpvAIr qOrSZGofNApNDWdrr5kYUh/qFGSkFKWu6BCPnJ+gVk77IRw1hdFYl7WiNrIRZJja cSrh7/Mj5EKxnb77Sg3nTOLeuRnztE4B6US5twBLQ4NvBrUC9ciMgBpfDc80XBLJ pfBBmerR8Snh3eJVYst3S6GwUXxipNILBDktURLw1C7bCnA8G5tO2rVlzcLdCTSH WncaYfPCHddxoQVG+01hWghQ0shscaRIQQDPM6DtlBE2APyBAvD4kh1BjdzxIGWs YHK1yCF4HL9s5oqB/z4j0IMPlxxoCOWs2RmxX4DxkYpXwTf5gpFUg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrheelgdehkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesghdtreertddtjeenucfhrhhomhepofgrgihimhgv ucftihhprghrugcuoehmrgigihhmvgestggvrhhnohdrthgvtghhqeenucggtffrrghtth gvrhhnpeeutdfgjeeuudehvefgvedvtedtudelfffgffekledtffekgedukeejueevieeg udenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmrg igihhmvgestggvrhhnohdrthgvtghh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 9 Feb 2022 09:04:34 -0500 (EST) Date: Wed, 9 Feb 2022 15:04:32 +0100 From: Maxime Ripard To: Jiaxun Yang Cc: Sui Jingfeng <15330273260@189.cn>, 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: <20220209140432.ekqszxbtitmacpk5@houat> References: <20220203082546.3099-1-15330273260@189.cn> <20220203082546.3099-2-15330273260@189.cn> <20220203085851.yqstkfgt4dz7rcnw@houat> <57805e19-285a-76d3-16e3-09a3eb7a9540@189.cn> <20220209085215.65qbdsgwtnvujdng@houat> <8e7f7946-b9e5-7c4d-f5c9-e091bf5f814b@flygoat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vl5too7ki5enoddb" Content-Disposition: inline In-Reply-To: <8e7f7946-b9e5-7c4d-f5c9-e091bf5f814b@flygoat.com> X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --vl5too7ki5enoddb Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 09, 2022 at 11:56:48AM +0000, Jiaxun Yang wrote: >=20 >=20 > =E5=9C=A8 2022/2/9 8:52, Maxime Ripard =E5=86=99=E9=81=93: > > On Thu, Feb 03, 2022 at 11:47:16PM +0800, Sui Jingfeng wrote: > [...] > > DT isn't really a solution either. Let's take the distribution > > perspective there. Suppose you're a Fedora or Debian developer, and want > > to make a single kernel image, and ship a DT to the user for their board > > without any modification. How is either the Kconfig solution or DT flags > > solution any good there? It doesn't help them at all. > > We are working in another way. As we can tell model of the board by strin= gs > passed from the firmware, we just built-in all poosible DTs into the kern= el > and then tell which DT to load at boot time. So we can ensure users has > smmoth experience. It's not really for you to say though. Once your driver is in a release, distros are going to use it. That's the whole point of you asking us to merge it. Maxime --vl5too7ki5enoddb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCYgPJ8AAKCRDj7w1vZxhR xQ7jAP9etfpiFR/7BaYwCwRPhBjfmYKdaCacf+X7uAN8xqcKDwD9FtD6v8xZ4gAL l00pbTcOa2efVrqJ8frFZMlTOvz47QI= =gzq+ -----END PGP SIGNATURE----- --vl5too7ki5enoddb--