Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp780585ybf; Sat, 29 Feb 2020 16:03:45 -0800 (PST) X-Google-Smtp-Source: APXvYqxKIBmkcbBNdNfVWOUV1jGI/QadW5y6mdPCJYCHbe87oQfPrd7OTGwdSO9UMJeAFkEVVywq X-Received: by 2002:a54:440e:: with SMTP id k14mr7176296oiw.160.1583021025805; Sat, 29 Feb 2020 16:03:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583021025; cv=none; d=google.com; s=arc-20160816; b=t1MzVNADx1WPF3MwuNtJncrabRzJVRNjJaedmpLyAmnOsvc+54a9fcPSmBYSKzwAvU TEDC0N0xS8EddVhKtFc61VW6hYiHwOorCkbRE95sjafmoN3EBypzJwCa0wHjGRaGEERV uL72vsMhVLLQ9CSGljmAdm4rf2pJAwIYtyRrBbxn203Xtu6dBRCh7CVlaEz4XbByDMcM dqFasGg9BlniPiRBoEQhdDvvM91Km1Rwq6hwe4D31U6v0fByNX8f0B6V+5HpA67KhDnt MMv+MPDuiLA9HBwdDCKx3uVkMY9hLlWBsr7Z+KbG/E6D3uHxG1BS4Urkps1VHM5M7fmo oF6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=iowDP25Wrbybi5vXfUtNN1vN/p40Bi133KSdqvrZpqM=; b=rEVDIiViYG5snKIL3pR6VifpxP/0Uk+qLhqP7d5LZgMolB7MoVgKsOiCIU4U25Zl7d rB10tSZbxYILmLxo+bsxWtbcu5IyT4UAgLoxsiJM5j8Q7c/rJVKOtKuAatMNFrTRhCFn /4LQ1retxZbRaRj4gfzRZYl3f0tXdMTBeWllrB8XuOJnc0nHR3Z1ixTUb/L65dJSC5qD TO792G3PKBGoWjx/PKayMlgjsH/HL3YmO/AJHnqUkRg6y2ODd282rrkQk2nqwqQ42IoR 264/5nKqI9T7+gWb7RhlC7BcVH7rHpBrnlO4vkmQIaWgzkY2n9xvJ52CIkApCEdpG2jU dMOQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z8si3722489otp.79.2020.02.29.16.03.33; Sat, 29 Feb 2020 16:03:45 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727210AbgCAACK (ORCPT + 99 others); Sat, 29 Feb 2020 19:02:10 -0500 Received: from gloria.sntech.de ([185.11.138.130]:55476 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727162AbgCAACJ (ORCPT ); Sat, 29 Feb 2020 19:02:09 -0500 Received: from p508fcd9d.dip0.t-ipconnect.de ([80.143.205.157] helo=phil.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1j8C3a-0004tG-JZ; Sun, 01 Mar 2020 01:02:06 +0100 From: Heiko Stuebner To: Johan Jonker , dianders@chromium.org Cc: Robin Murphy , devicetree@vger.kernel.org, robh+dt@kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org Subject: Re: [PATCH 3/4] dt-bindings: arm: fix Rockchip rk3399-evb bindings Date: Sun, 01 Mar 2020 01:02:06 +0100 Message-ID: <3089122.gegXmbq47i@phil> In-Reply-To: <229c3511-d99d-8bac-6241-0088c5fc13ef@gmail.com> References: <20200228061436.13506-1-jbx6244@gmail.com> <78b8b53f-2e2a-3804-41fb-bb2610947ca2@arm.com> <229c3511-d99d-8bac-6241-0088c5fc13ef@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Johan, Am Freitag, 28. Februar 2020, 14:28:36 CET schrieb Johan Jonker: > Hi Robin, > > When I look at the review process of rk3399-evb.dts > it is mentioned here: > > https://lore.kernel.org/patchwork/patch/672327/ > > >> + model = "Rockchip RK3399 Evaluation Board"; > >> + compatible = "rockchip,rk3399-evb", "rockchip,rk3399", > >> + "google,rk3399evb-rev2", google,rk3399evb-rev1", > >> + "google,rk3399evb-rev0" ; > > > > can you check against which compatibles that coreboot really matches? > > > > As we said that the evb changed between rev1 and rev2, I would expect the > > compatible to be something like > > > > compatible = "rockchip,rk3399-evb", "google,rk3399evb-rev2", > > "rockchip,rk3399"; > > > > leaving out the rev1 and rev0 > > The consensus in version 4 ends in what is shown in the dts file, so I > changed it in rockchip.yaml. Things from the past maybe can better be > explained by Heiko. Please advise if this patch needs to change and in > what file. Just get rid of the "google,rk3399evb-rev2" from the .dts please :-) . (1) "rockchip,rk3399-evb", "rockchip,rk3399", "google,rk3399evb-rev2"; is just wrong for the reasons Robin explained, I guess that slipped through review at the time. (2) "google,rk3399evb-rev2" was a specific variant for Google I'm pretty sure they'll have scraped all these boards directly after they had the first actual rk3399-gru development devices So I'm pretty sure the only rk3399-evbs in existence are the general ones. Heiko