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 288F6C71133 for ; Fri, 25 Aug 2023 12:02:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239699AbjHYMBp (ORCPT ); Fri, 25 Aug 2023 08:01:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58416 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239941AbjHYMBh (ORCPT ); Fri, 25 Aug 2023 08:01:37 -0400 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.153.233]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AC39F198E for ; Fri, 25 Aug 2023 05:01:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1692964895; x=1724500895; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=ZeZyfeKGvQL1c/itO010dweirYa6Wn++IE4GN+lXY78=; b=uLcCzs8UtkhbzBbIJXwvw7CcbMs9Gmf+/lVaNxTS3Jta3nTkJXQh5kLI KU6DuNadq1WSlC2kdS6GzRV6+JdmQd1DwMkvrHnr5NvaUd8lU+FEjNTaD fYVWb/WmFkO3DtU2ZCyNYSYlEjexxcPsCv5hOXCKlScUbSwS6e6oNX0bm QBWDqOD+AITwblaVXERh23ef+/7Z3tSGR4TLQW0VzD9E7TsPREErKpMWS l8I0LSUbZV7kDTEpG3/aRarfiuHabdIiVdMqBnHwRAKn11cCkt4D8Uxyc EawGHRnhnkYClCXS2qT0gfMQoK4EN3hRZEKjaddZl/gDYltzDUZ2gPQuC Q==; X-IronPort-AV: E=Sophos;i="6.02,195,1688454000"; d="asc'?scan'208";a="1305684" X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa1.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 25 Aug 2023 05:01:34 -0700 Received: from chn-vm-ex04.mchp-main.com (10.10.85.152) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Fri, 25 Aug 2023 05:01:33 -0700 Received: from wendy (10.10.85.11) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21 via Frontend Transport; Fri, 25 Aug 2023 05:01:31 -0700 Date: Fri, 25 Aug 2023 13:00:50 +0100 From: Conor Dooley To: Binbin Zhou CC: Rob Herring , Binbin Zhou , Huacai Chen , Krzysztof Kozlowski , Conor Dooley , , Huacai Chen , , Xuerui Wang , , Jiaxun Yang , Hongliang Wang Subject: Re: [PATCH v4 3/7] LoongArch: Allow device trees to be built into the kernel Message-ID: <20230825-hypocrite-smoking-cc6ce8c2936b@wendy> References: <3e69929008c8190cff331941dd4d34f748e5e44a.1692783907.git.zhoubinbin@loongson.cn> <20230823194250.GA2768550-robh@kernel.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KsqxT0t8TAxpVqE1" Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org --KsqxT0t8TAxpVqE1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 24, 2023 at 11:20:34AM +0800, Binbin Zhou wrote: > Hi Rob: >=20 > On Thu, Aug 24, 2023 at 3:42=E2=80=AFAM Rob Herring wro= te: > > > > On Wed, Aug 23, 2023 at 05:54:51PM +0800, Binbin Zhou wrote: > > > Some systems do not provide a useful device tree to the kernel at boot > > > time. Let's keep a device tree table in the kernel, keyed by the dts > > > filename, containing the relevant DTBs. > > > > Support for this in other arches was added to support legacy bootloaders > > with no DT support. You should not need this for a new architecture. Fix > > the bootloader to provide a useful DT. > > > Yes, our bootloader already supports DT. >=20 > Our original intention of providing kernel built-in DTS is to describe > all possible device information of that SoC, so that everyone can use > it as a reference during development; we will unlikely to add more > .dts files to the kernel besides the reference ones. >=20 > And as a reference, our built-in DTS provides the most basic bootable > combinations (so it is generic enough) as an alternative in case the > DTS in the bootloader is unexpected. >=20 > Does this make any sense? I don't see how this answers the question - as far as I can tell Rob was asking specifically about the building the dtb into the kernel, whereas your response seems to talk about havint the dts files in the kernel tree. --KsqxT0t8TAxpVqE1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZOiX8QAKCRB4tDGHoIJi 0mMdAQCaaVLfZyKQ+j/RLCRL7NKg22cLE3B7zY7QFUv8jaSxEQD+POPxvl8zvCSb lmpG4BcHfRU8QKAVQj8AuJ57nfm8eg0= =9MR/ -----END PGP SIGNATURE----- --KsqxT0t8TAxpVqE1--