Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp176668ybm; Thu, 28 May 2020 19:45:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy2MvkHTdVQ6/5hSJhRHhvEoOwE1ewildo3D5kjil3el7FGC0BHGleWwb2/m3UDfOeUA/qg X-Received: by 2002:a17:906:bcc5:: with SMTP id lw5mr5899835ejb.470.1590720330310; Thu, 28 May 2020 19:45:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590720330; cv=none; d=google.com; s=arc-20160816; b=KTe8ySGTaDZBhJsiUIvB+b1UeoBrluXcfW3LsrOPQbzM2s8ke4MWri1ZAI3XbXiFZt 7L2ChHwVx5k/Zq5zfhbMZVJC/3FUjtrMd3IcUxvLOovlSz8u+tv9SuUNt9hwJebJN8NZ JOif7jWKTjsHgUh+6wmLsOwMgb+vkDJZXNmJs/4YdfI500b5MY8GvBWo43ot/YevmIW8 e5yjLcqfJtyyidmx0aaspvxwOYwbfnSjx7UcDuEyuC/6bT30Vrk2o43R5jMrD+GXRsNw GCcDH7UKUuAnfNG+VElkAEKcIOFoNA9je/vggvzS8oZRk6sGWfi4EcyWi7dNk441cSdZ eeqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date; bh=Q5A/JMcrxs2NkbJ3X4VaAOZxIF6XFCky8rmhUvFQDyY=; b=EBz7SW3AmH+tgQbqjKmr4H+TECg3+p0y9A1GpK+V5QC0pjXd8maKMek+oPA+xwbfzQ hJrUEYjXaT65TfJE0+1qJSptIWcnoIWr1DxPAuSrNmc8Ef+9Tn6rSvas1vlrjqTbg5c0 QrT5uYO0k981kXAHL9ZN7P8E6dZ6qq0tQWY1OTB3VfLwdzM0Ct52zrxFFP9GSKYZkmlh gVIqx2q+k9KvUN5Q6TXseMV5FZxyXPYt/KnHQy663JQTcg7R6pIMLWbfJ8umt4J91WJC FUl4udAvRD5EfAJZ78qlPbdi2RNGVzvwbxSc5xujEXE/iBMROuWSWkzKm+4BVNzeaa5q Bu1w== 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 n6si5176667eda.5.2020.05.28.19.45.06; Thu, 28 May 2020 19:45:30 -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 S2391601AbgE2Cl5 (ORCPT + 99 others); Thu, 28 May 2020 22:41:57 -0400 Received: from relmlor1.renesas.com ([210.160.252.171]:7473 "EHLO relmlie5.idc.renesas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2389601AbgE2Cl4 (ORCPT ); Thu, 28 May 2020 22:41:56 -0400 Date: 29 May 2020 11:41:53 +0900 X-IronPort-AV: E=Sophos;i="5.73,447,1583161200"; d="scan'208";a="48301692" Received: from unknown (HELO relmlir5.idc.renesas.com) ([10.200.68.151]) by relmlie5.idc.renesas.com with ESMTP; 29 May 2020 11:41:53 +0900 Received: from mercury.renesas.com (unknown [10.166.252.133]) by relmlir5.idc.renesas.com (Postfix) with ESMTP id 9AF25400F92F; Fri, 29 May 2020 11:41:53 +0900 (JST) Message-ID: <87imgfzclq.wl-kuninori.morimoto.gx@renesas.com> From: Kuninori Morimoto To: Rob Herring Cc: Liam Girdwood , Mark Brown , Mark Rutland , devicetree@vger.kernel.org, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Subject: Question about "xxx,yyy" style property In-Reply-To: <20200528223916.GA804926@bogus> References: <87pnay3ptb.wl-kuninori.morimoto.gx@renesas.com> <20200528223916.GA804926@bogus> User-Agent: Wanderlust/2.15.9 Emacs/25.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") 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 The Subject was "Re: [PATCH] ASoC: dt-bindings: simple-card: care missing address #address-cells" Hi Rob I'm trying to create v2 of simple-card patch, And got issue which I can't solve by myself. I think "xxx,yyy" (= which has "," at the property name) needs special care, but it is very un-understandable... Now, I'm give up. So, can I ask you 2 things about Yaml Doc "xxx,yyy" type property ? ======================== 1) reference own definitions from "xxx,yyy" ======================== I guess "xxx,yyy" naming property needs to has "description", right ? But, it is OK if it references "/schemas/xxxx" --- OK ------ xxx,yyy: description: xxx $ref: /schemas/types.yaml#/definitions/phandle-array ------------- but, will be error if it references own definitions --- NG ------ xxx,yyy: description: xxx $ref: "#/definitions/mydef" ------------- This is the related error -- error(?) -- xxx.yaml: properties:xxx,yyy:\ $ref: '#/definitions/mydef' does not match 'types.yaml#[/]{0,1}definitions/.*' -------------- # but, there is no problem if it was defined as "patternProperties" Q. The "xxx,yyy" property can't references own definitions, or needs some magical extra settings ?? ======================== 2) phandle for "xxx,yyy" ======================== I noticed that it seems "xxx,yyy" property can't be referenced. Here, "xxx,yyy" has "type: object" and "additionalProperties: false" (below didn't happen if it doesn't have "additionalProperties: false") If "xxx,yyy" has phandle, but not referenced, This is not a problem. --- OK --- ... foo = <&bar>; ... xxx_yyy: xxx,yyy { ... }; -------------- But will be error if it is referenced. --- NG --- foo = <&xxx_yyy>; ... xxx_yyy: xxx,yyy { ... }; ------------ The error is -- error --- xxx.yaml: xxx.yyy: \ Additional properties are not allowed ('phandle' was unexpected) ------------ Q. The "xxx,yyy" needs magical settings to be referenced, or can't be ?