Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp5565279ybl; Tue, 27 Aug 2019 06:38:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqzQQEEtNQQTgv/rK3MQ537bSBwVCJ2QcT90uYtSXBQqhhG3i9zVfSYJR7SFKFCXL3oOnZaq X-Received: by 2002:a63:e807:: with SMTP id s7mr20651398pgh.194.1566913113659; Tue, 27 Aug 2019 06:38:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566913113; cv=none; d=google.com; s=arc-20160816; b=qTLA0u7SVRQ7ZzJ5s1aE+7MGdjUXqNwkLLjIhsBmGubDsEZ9XDKAS+xVzo4mDW0gDY ae80/Gy4ImRjVa0vfVcLoFTqX0anWN/5VmBlGg7GjpWLM+ZQ6ay5U+I3UZz0HpfRDq66 sO3XIcfU4nxzvMsqUvcsWPd//pDr3pmT7TFr5mxJja1uRm939gsmVasjoFqv6kU9DROV //dO6O4TvbpPQlm5Pbpuu18Wl4pnriwt5GBJa7A4wLCIwIizRe/R/zvBqveYkq9+2iy5 a1AotVtyXUnuVuM8DhzlbiDBmnk3e0ejy8Y4JApG2oAi2C4OfykDsn4UnwR72xhMLLo2 5oMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=i+WbRkN4627Y1ukP49Xm1Eb8jHha+UR8bl8/oDFjtVo=; b=EzrqDc9iaPnWDSVUW59HMr1o4BEtJEeBmgMAsGMmIA4rLCWi6BeUOVhxSJ6lLVwsnI gLNuGuaHmw71PDiDeyckoMTrWaMncYKveFcAAx/3BIEV0A8nhU2JpulDxPc9nY58TSMA 2Hj6h6KAIUrF3wiBP6TQAklXFkfUefjoSF1SgvNnS3aYp7Oes8hxaxmoO47VygxsU2p/ nCDKN2OIE4M4UJ8Ii4ztvMZqkb/JgbAFf7T6CUwPUXuRzWoHtmJ9LbnaSdOGk8k1HVu5 UuUKSZYBn3u/qdnwQv/Z7EcJfr8J4EPqZRyW5oBN36IIMIz2PPZyUyVc1zSG3KnO9PnI 1fIw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=iIHtOikM; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m6si12010492pgp.423.2019.08.27.06.38.18; Tue, 27 Aug 2019 06:38:33 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=default header.b=iIHtOikM; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728803AbfH0NhB (ORCPT + 99 others); Tue, 27 Aug 2019 09:37:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:52158 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725811AbfH0NhB (ORCPT ); Tue, 27 Aug 2019 09:37:01 -0400 Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com [209.85.160.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A82A820673; Tue, 27 Aug 2019 13:36:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566913019; bh=mD4q3LMo8D/oOkYLDOKCUAJJn9XFxRojkzOMMIIoH1I=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=iIHtOikMNFdIzPT8jWOw/5DwxGlxnvIEDZv9e0PiIiaJHWvdLX+iDsXGeyppF1TUt c17W7Fc/T4Ik+b8XGYSHnukX7bjPDJcSTOeFIdDfjLuyWZrYhffCGT6g1hesZDhpUj 3ZgF2FfSALXvFmHTL98And13MaG/+fN4e5USc9s4= Received: by mail-qt1-f177.google.com with SMTP id z4so21308542qtc.3; Tue, 27 Aug 2019 06:36:59 -0700 (PDT) X-Gm-Message-State: APjAAAU7mfZwakEtztu/sMj5ID/Uyt9AY8SLd0ZRYKMJM4kH7V8NLZ/0 ok97OqN9a2T9MWbWZlAgsWg3nUEhOCJIEReUwQ== X-Received: by 2002:a0c:eb92:: with SMTP id x18mr20126969qvo.39.1566913018683; Tue, 27 Aug 2019 06:36:58 -0700 (PDT) MIME-Version: 1.0 References: <20190822092643.593488-1-lkundrak@v3.sk> <20190822092643.593488-3-lkundrak@v3.sk> <136a57cf3d293e3233f31d5ee660a6418726333a.camel@v3.sk> In-Reply-To: <136a57cf3d293e3233f31d5ee660a6418726333a.camel@v3.sk> From: Rob Herring Date: Tue, 27 Aug 2019 08:36:47 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 02/20] dt-bindings: arm: Convert Marvell MMP board/soc bindings to json-schema To: Lubomir Rintel Cc: Olof Johansson , Mark Rutland , Thomas Gleixner , Jason Cooper , Marc Zyngier , Kishon Vijay Abraham I , Russell King , Michael Turquette , Stephen Boyd , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linux-clk Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 27, 2019 at 8:24 AM Lubomir Rintel wrote: > > On Tue, 2019-08-27 at 06:59 -0500, Rob Herring wrote: > > On Thu, Aug 22, 2019 at 4:27 AM Lubomir Rintel wrote: > > > Convert Marvell MMP SoC bindings to DT schema format using json-schema. > > > > > > Signed-off-by: Lubomir Rintel > > > > > > --- > > > Changes since v1: > > > - Added this patch > > > > > > .../devicetree/bindings/arm/mrvl/mrvl.txt | 14 --------- > > > .../devicetree/bindings/arm/mrvl/mrvl.yaml | 31 +++++++++++++++++++ > > > 2 files changed, 31 insertions(+), 14 deletions(-) > > > delete mode 100644 Documentation/devicetree/bindings/arm/mrvl/mrvl.txt > > > create mode 100644 Documentation/devicetree/bindings/arm/mrvl/mrvl.yaml > > > > > > diff --git a/Documentation/devicetree/bindings/arm/mrvl/mrvl.txt b/Documentation/devicetree/bindings/arm/mrvl/mrvl.txt > > > deleted file mode 100644 > > > index 951687528efb0..0000000000000 > > > --- a/Documentation/devicetree/bindings/arm/mrvl/mrvl.txt > > > +++ /dev/null > > > @@ -1,14 +0,0 @@ > > > -Marvell Platforms Device Tree Bindings > > > ----------------------------------------------------- > > > - > > > -PXA168 Aspenite Board > > > -Required root node properties: > > > - - compatible = "mrvl,pxa168-aspenite", "mrvl,pxa168"; > > > - > > > -PXA910 DKB Board > > > -Required root node properties: > > > - - compatible = "mrvl,pxa910-dkb"; > > > - > > > -MMP2 Brownstone Board > > > -Required root node properties: > > > - - compatible = "mrvl,mmp2-brownstone", "mrvl,mmp2"; > > > diff --git a/Documentation/devicetree/bindings/arm/mrvl/mrvl.yaml b/Documentation/devicetree/bindings/arm/mrvl/mrvl.yaml > > > new file mode 100644 > > > index 0000000000000..dc9de506ac6e3 > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/arm/mrvl/mrvl.yaml > > > @@ -0,0 +1,31 @@ > > > +# SPDX-License-Identifier: GPL-2.0 > > > +%YAML 1.2 > > > +--- > > > +$id: http://devicetree.org/schemas/arm/mrvl/mrvl.yaml# > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > + > > > +title: Marvell Platforms Device Tree Bindings > > > + > > > +maintainers: > > > + - Lubomir Rintel > > > + > > > +properties: > > > + $nodename: > > > + const: '/' > > > + compatible: > > > + oneOf: > > > + - description: PXA168 Aspenite Board > > > + items: > > > + - enum: > > > + - mrvl,pxa168-aspenite > > > + - const: mrvl,pxa168 > > > + - description: PXA910 DKB Board > > > + items: > > > + - enum: > > > + - mrvl,pxa910-dkb > > > > Doesn't match what's in dts file: > > > > arch/arm/boot/dts/pxa910-dkb.dts: compatible = > > "mrvl,pxa910-dkb", "mrvl,pxa910"; > > It corresponds to the .txt bindings specification this commit is > converting. I thought it wouldn't be a good idea to do any changes to > the contents at the time the conversion is done. There are so many errors like this, that it's fine to do it in the conversion. A separate patch is fine too. > I also don't understand why does the dts file specify the board- > specific compatible string. Surely "mrvl,pxa910" alone would be > sufficient? To potentially work around any board specific issue without a dtb change. > > > > + - description: MMP2 Brownstone Board > > > > If this entry is only for this board... > > > > > + items: > > > + - enum: > > > + - mrvl,mmp2-brownstone > > > > ...then this can be a 'const' instead. Same for the others. > > Sure, but is it preferable? I've actually done a "git grep -A3 enum > Documentation/devicetree/bindings/" to see if the single-element is > typically used and it seems like it is. Perhaps it's a good idea to > indicate to a human reader that this is a list that's expected to > eventually be extended with new elements. Then the description should match and say 'MMP2 based boards'. > In any case, there are more boards with MMP2 currently supported, > notably the XO-1.75 laptop. I've actually sent out the dts file for > review some time ago. I haven't added a separate compatible string for > it because I thought it is not necessary (see above). You should add one. Rob