Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp4281739pxy; Tue, 27 Apr 2021 00:52:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJykng64Wk4W13Y+riicogQTEJmOTHxT9xe4QQc6u478YVICu8hzx9higNGrK5q2rHkk8peV X-Received: by 2002:aa7:dbcd:: with SMTP id v13mr2759070edt.59.1619509964980; Tue, 27 Apr 2021 00:52:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619509964; cv=none; d=google.com; s=arc-20160816; b=hkIpVfOz0mxmyVs5QYMRm+HRAzacsrxfbFhPSAngGT13VDMQponNbA2ATwidjj9Y6E 9n+SFlh5EZU4LsSQf7WkwY7Ia9BVtcUB9fIbOhtvwsZWTDNJFchG0SmdEUMEwndU1KwL bPaunuIQ71u09TSgtnp6n4ETMU1Qgq3J3oru0XSbLzaDXplUiyOkTt92Kp+PuCXaypGc tJpoeEKIW3lVRFF/MGiMRbLG23LAq698y/V8OkQpW04cFgf9ZE5sGtLLMWlf1Wue8vB3 2a/zxzIP6r3ZOtEl4Ozho9LebnnKLgx6R8sUZtlS6xrFnvY1M5N0biNFXfUfgVjlLZnW ZfoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=f8rWo79Dhad6woSPzuO+4a6RS5tbL+n01Y12CbHr+Vc=; b=G6t08KWbEdZLoL78B9i0jGFPueQMO8FHpFmspF/jWc32LrG3KQl26phQpCaelyJS2K /5w6knbV8Zsgq8RyU8NsNjJ+Mi+Hj0hQhZBsgAjVfMzSVASW0Bx0ylO7A/rfa1vEP9pu BVPRg1OW3jhFutU0T5zXMkRrdlWjffGQbJfuDjpWRMJsvTXadSFOMrW0eQmp1l3JYdtD M+Dq2y0VeckjimmqozBVnlkj9zCUNX3X3+6Nx2PlhKxhM0YlfG9qtFLVuKUTreW9i32z DKdl7IH9mneHnGZFn1Y9vsWK+YfXPC4w+4sd7An+mbMGZdGt7+5tWyEzk5dNa8+2g5f4 Ac4A== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hq21si57544ejc.224.2021.04.27.00.52.21; Tue, 27 Apr 2021 00:52:44 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234920AbhD0HuA convert rfc822-to-8bit (ORCPT + 99 others); Tue, 27 Apr 2021 03:50:00 -0400 Received: from gloria.sntech.de ([185.11.138.130]:51040 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230255AbhD0Ht7 (ORCPT ); Tue, 27 Apr 2021 03:49:59 -0400 Received: from ip5f5aa64a.dynamic.kabel-deutschland.de ([95.90.166.74] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lbISa-0002Fw-Pi; Tue, 27 Apr 2021 09:48:44 +0200 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Johan Jonker , cl@rock-chips.com, Kever Yang Cc: robh+dt@kernel.org, jagan@amarulasolutions.com, wens@csie.org, uwe@kleine-koenig.org, mail@david-bauer.net, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, jensenhuang@friendlyarm.com, michael@amarulasolutions.com, cnsztl@gmail.com, devicetree@vger.kernel.org, ulf.hansson@linaro.org, linux-mmc@vger.kernel.org, gregkh@linuxfoundation.org, linux-serial@vger.kernel.org, linux-i2c@vger.kernel.org, jay.xu@rock-chips.com, shawn.lin@rock-chips.com, david.wu@rock-chips.com, zhangqing@rock-chips.com, huangtao@rock-chips.com, wim@linux-watchdog.org, linux@roeck-us.net, jamie@jamieiles.com, linux-watchdog@vger.kernel.org Subject: Re: [PATCH v2 6/7] arm64: dts: rockchip: add core dtsi for RK3568 SoC Date: Tue, 27 Apr 2021 09:48:41 +0200 Message-ID: <2088315.NnIJQXNAa5@diego> In-Reply-To: References: <20210425094216.25724-1-cl@rock-chips.com> <3d584cdc-020e-5aae-cae3-59ef45e64a9f@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Am Dienstag, 27. April 2021, 05:45:03 CEST schrieb Kever Yang: > Hi Johan, Heiko, > > On 2021/4/26 下午8:16, Johan Jonker wrote: > > === > > > > compatible = "rockchip,rk3568"; > > Maybe add this together with other rkXXXX SoCs to rockchip.yaml on top > > of board list ??? > > Please advise. I don't think so. I.e. the rockchip,rk3568 compatible is not supposed be standing alone somewhere, but should always be combined with a board- compatible. Same as the rk3568.dtsi should not be used alone but included into a board dts. And patch7 does this by adding the necessary entry to the board list. > This rockchip.yaml is now describe boards without any sort, it would be > better to refactor and sort in two level: > - soc level > - board level base on the same soc. The sorting in rockchip.yaml is supposed to be alphabetically by description. (vendor + boardname) My intention for this was to allow readers to find their board to get the matching compatible - and I like that ordering somehow ;-) . So I don't think there are bigger changes necessary to rockchip.yaml Heiko