Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1221125ybh; Thu, 16 Jul 2020 06:35:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzyHzBWUB77UHfMrRhHhEj9+hV1b6Z9EhH+khREGAWJhR1ul5UBm13Ay9WfPYV2eZsVPhKM X-Received: by 2002:a17:906:6606:: with SMTP id b6mr3968259ejp.102.1594906524617; Thu, 16 Jul 2020 06:35:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594906524; cv=none; d=google.com; s=arc-20160816; b=KPppVj6fw3vCRPOcs9/ESFTdD7I16nhQIwKLHqytMaivtiDbxVZnrK4mMjPD5h2Hff //fisc1D0hUygmUIWNOdJ18D4vu3Z0yPGv1P50zWKkIU1G9jvrJ2eY4BMgIz+zhqfZZh QQRKw369r9vTOeUVYL34BqBg9kHab4IruWmrOBSD6frVBZP7NPCBt/VONGrqowGsp4Ku +JOimnCigRzu7YDmqH5AjsabvSCQozdMPfHAyau7vuIqx5U8sC8v/11RjJ5U61u4LzhA o4IR7utWO4tC85s/Kz+tegDewmtLJtcktKA1hjMnSffueaAhqEhzfb8htX/nuoGfhN4w cDsw== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=U+l7F8Gifju4m7HssmZLwA3C/J9CbppLGBEJ2Nwu/Q8=; b=NGO+u4kQXKLjiXOZVX5jNYLIgTGp6bhHs4r3MwDApIoKMFRbFFKypgOoHNrgplxBt7 T2FJMO1/GA08swHzmxJCZ3fKSKM1U7TBdHB7YLDv9Ty50sK4EygDeTbvgFRp8DptJtOA sOlNGYpHmnHvuqHHvsWu35JmkUD6PpGGjMo3H2fVAw3DcAGoJSDAhyFnJTrP2SlrSg/q +mGOaHyJ7Fc+g9Z3Wg3hRlzcedPqqO8HLCQDmvRLVu+cgHMEePi1tEBCjccTIlyAKJ+2 MhCeao1/UAdgJphWOp0NzbdiLMYJN8CvMZQPb+3fsIf4x1c2mpusbuqJAgc7dJD5S+t7 JIsA== 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 h8si2953236edn.92.2020.07.16.06.35.01; Thu, 16 Jul 2020 06:35:24 -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 S1728439AbgGPNeN (ORCPT + 99 others); Thu, 16 Jul 2020 09:34:13 -0400 Received: from foss.arm.com ([217.140.110.172]:49518 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725975AbgGPNeM (ORCPT ); Thu, 16 Jul 2020 09:34:12 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id E07F331B; Thu, 16 Jul 2020 06:34:11 -0700 (PDT) Received: from [10.57.35.46] (unknown [10.57.35.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id CD2E63F66B; Thu, 16 Jul 2020 06:34:09 -0700 (PDT) Subject: Re: [RFC PATCH v1 1/2] dt-bindings: arm: rockchip: add A95X Z2 description To: Johan Jonker , Rob Herring Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, heiko@sntech.de, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org References: <20200620134659.4592-1-jbx6244@gmail.com> <20200620134659.4592-2-jbx6244@gmail.com> <20200715192935.GA684031@bogus> <14b39efe-f38b-b471-560d-1ecaeafc5dd5@gmail.com> From: Robin Murphy Message-ID: <56b1447d-6c62-9e73-a7ce-08fb70096a97@arm.com> Date: Thu, 16 Jul 2020 14:34:08 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <14b39efe-f38b-b471-560d-1ecaeafc5dd5@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-07-16 13:05, Johan Jonker wrote: > Hi Rob, > > The A95X Z2 boxes are sold by various vendors/manufacturers/web shops. > The box it self only shows a label with a model name. > Determining the true vendor is a kind of tricky for a outsider of the > business. > Could you advise what would be a save choice to the rather rigid vendor > requirements. > Is for example this a option: > > "^a95x,.*": > description: A95X > > Is there someone who can give more info on this subject? FWIW we already have some "A95X" branded things attributed to Nexbox in upstream DTs, however, the evidence from scraping around the internet suggests that the closest thing to an original vendor for the "A95X Z2" model is probably these folks: https://zkmagic.en.alibaba.com/ Robin. > > Kind regards, > > Johan Jonker > > On 7/15/20 9:29 PM, Rob Herring wrote: >> On Sat, Jun 20, 2020 at 03:46:58PM +0200, Johan Jonker wrote: >>> Add A95X Z2 description for a board with rk3318 processor. >>> >>> Signed-off-by: Johan Jonker >>> --- >>> Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++ >>> 1 file changed, 5 insertions(+) >>> >>> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml >>> index d4a404509..3d44b3cf0 100644 >>> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml >>> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml >>> @@ -25,6 +25,11 @@ properties: >>> - const: vamrs,rock960 >>> - const: rockchip,rk3399 >>> >>> + - description: A95X Z2 >>> + items: >>> + - const: a95x,z2 >> >> Need to document vendor prefix. >> >>> + - const: rockchip,rk3318 >>> + >>> - description: Amarula Vyasa RK3288 >>> items: >>> - const: amarula,vyasa-rk3288 >>> -- >>> 2.11.0 >>> > > > _______________________________________________ > Linux-rockchip mailing list > Linux-rockchip@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-rockchip >