Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp3683193imm; Mon, 8 Oct 2018 07:58:24 -0700 (PDT) X-Google-Smtp-Source: ACcGV632pToF0xLvR6NIoATIZ5yATA20bE3PwLhn1yTt+9H5uDOQIQdPaj1h6zaH6irvI7kDCSGI X-Received: by 2002:a17:902:708a:: with SMTP id z10-v6mr13380256plk.330.1539010704841; Mon, 08 Oct 2018 07:58:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539010704; cv=none; d=google.com; s=arc-20160816; b=A7l+huIKz8EZ5kJIlluYjGyF4JueWfLkQ0iwrXqtrM/HA9JSFatTpGrkeSEc5AGQvA kNTj+RN6WoNTrSKUiJ52EK+0Pl6CAvDBlL5dVQvaXyh1XiiKlJY1OhhmMqmxm+3CMRz0 5ldbVsa7tQsvjbvgmCPYColIdGe8TV1iHgsjROdYAXP5ROT6lV3sg5mOe01WSf4Z2sJF s6PF5OKK81twlNdm6wWa5hRUTbn0OUW/PfkyIYjXuyr3nVY3UIxp3T5OkiqRrfAnE27M rr5umcmduW02TCincDkVDxcIHyNnxU1dkNstVQLVYM1EqLo0+01A3s6UUw5eZA4cYsOE LmmA== 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=qjweadokD2OohgI6HEkXKscnIn0D8bnEtLhiIbzWrLQ=; b=U+zeGN3075IZjrNw4+7RX8bejW7TsFgRVLfk36e27OGaVhBb/YXVbN9+bKhOmmieuf i79OgOFgqfunrZqnwzK17SacBuFfuMz2BSwNGmcah2HYrY/3n1GnB+aLmw+hACTKqsPT AaQibcUgfHCyc97gq6U5j0Oycl1P4/ZZZUFA2litkEhkVQceB0rbqhkBM8HsqjG7vqyE YlS9b8RFkEsY1cbV+uaZ6HYUracJuXm2plHmardtmgcaoFbJZZBDRt2QvchAjGZtHda8 tW4KqhfnkaRHvaKX7IYIO3AEcZhNBvVYUA8pWPfpsRq1aGUyb3F7fq14HwrNmn43N6/H KfjQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=bCnhnp4e; 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 l191-v6si16404309pgd.543.2018.10.08.07.58.08; Mon, 08 Oct 2018 07:58:24 -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=bCnhnp4e; 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 S1726452AbeJHWJt (ORCPT + 99 others); Mon, 8 Oct 2018 18:09:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:47986 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726078AbeJHWJt (ORCPT ); Mon, 8 Oct 2018 18:09:49 -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 80B1C20878; Mon, 8 Oct 2018 14:57:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539010660; bh=1BE0fw0J6LIRJq+p2GmA36rsVMGIZ+lKvwe/cLY4HQ4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=bCnhnp4eEYFxEFqoMCY9JW1YwDB+SeXXDDy93WH/q+eQDWTjLvq/gvYJ6N6n07q88 qLIOnplc7iJ159v2Rokq0QuUIGqWQyKPalB+hBV78PfFQjIzsJSOWWVO5hXRTttpUk tYhiwrZwB4Crt04GY7BpI1IclcAD3ZKwyZqR8o5c= Received: by mail-qt1-f177.google.com with SMTP id b4-v6so13174613qtc.7; Mon, 08 Oct 2018 07:57:40 -0700 (PDT) X-Gm-Message-State: ABuFfohtIH7TizgdpuP+k4v0cZr8xEyjneGdjBJqemuVvMi3XW/BnnyW rw3DSxrLpglDAK2tDSYooR5KO3FaessO7J56Hw== X-Received: by 2002:a0c:bc03:: with SMTP id j3-v6mr19885313qvg.77.1539010659716; Mon, 08 Oct 2018 07:57:39 -0700 (PDT) MIME-Version: 1.0 References: <20181005165848.3474-1-robh@kernel.org> <20181005165848.3474-30-robh@kernel.org> In-Reply-To: From: Rob Herring Date: Mon, 8 Oct 2018 09:57:27 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 29/36] dt-bindings: arm: Convert Renesas board/soc bindings to json-schema To: Geert Uytterhoeven Cc: "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linuxppc-dev , Grant Likely , Kumar Gala , Frank Rowand , Mark Rutland , Linus Walleij , Olof Johansson , Arnd Bergmann , Mark Brown , Tom Rini , Pantelis Antoniou , Jonathan Cameron , Bjorn Andersson , Simon Horman , Magnus Damm , "open list:MEDIA DRIVERS FOR RENESAS - FCP" 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 Mon, Oct 8, 2018 at 2:47 AM Geert Uytterhoeven wrote: > > Hi Rob, > > On Fri, Oct 5, 2018 at 6:59 PM Rob Herring wrote: > > Convert Renesas SoC bindings to DT schema format using json-schema. > > > > Cc: Simon Horman > > Cc: Magnus Damm > > Cc: Mark Rutland > > Cc: linux-renesas-soc@vger.kernel.org > > Cc: devicetree@vger.kernel.org > > Signed-off-by: Rob Herring > > Thanks for your patch! > > Note that this will need a rebase, as more SoCs/boards have been added > in -next. > > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/arm/shmobile.yaml > > @@ -0,0 +1,205 @@ > > +# SPDX-License-Identifier: None > > The old file didn't have an SPDX header, so it was GPL-2.0, implicitly? Right. I meant to update this with something. I'd prefer it be dual licensed as these aren't just kernel files, but I don't really want to try to gather permissions from all the copyright holders. And who is the copyright holder when it is implicit? Everyone listed by git blame? > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/bindings/arm/shmobile.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Renesas SH-Mobile, R-Mobile, and R-Car Platform Device Tree Bindings > > + > > +maintainers: > > + - Geert Uytterhoeven > > Simon Horman (supporter:ARM/SHMOBILE ARM ARCHITECTURE) > Magnus Damm (supporter:ARM/SHMOBILE ARM ARCHITECTURE) > > You had it right in the CC list, though... I generated it here from git log rather get_maintainers.pl because get_maintainers.pl just lists me for a bunch of them. > > + - description: RZ/G1M (R8A77430) > > + items: > > + - enum: > > + # iWave Systems RZ/G1M Qseven Development Platform (iW-RainboW-G20D-Qseven) > > + - iwave,g20d > > + - const: iwave,g20m > > + - const: renesas,r8a7743 > > + > > + - items: > > + - enum: > > + # iWave Systems RZ/G1M Qseven System On Module (iW-RainboW-G20M-Qseven) > > + - iwave,g20m > > + - const: renesas,r8a7743 > > + > > + - description: RZ/G1N (R8A77440) > > + items: > > + - enum: > > + - renesas,sk-rzg1m # SK-RZG1M (YR8A77430S000BE) > > This board belongs under the RZ/G1M section above > (see also the 7743 in the part number). Indeed. Not sure how I screwed that one up. > > + - const: renesas,r8a7744 > > > + - description: Kingfisher (SBEV-RCAR-KF-M03) > > + items: > > + - const: shimafuji,kingfisher > > + - enum: > > + - renesas,h3ulcb > > + - renesas,m3ulcb > > + - enum: > > + - renesas,r8a7795 > > + - renesas,r8a7796 > > This looks a bit funny: all other entries have the "const" last, and > use it for the > SoC number. May be correct, though. > To clarify, this is an extension board that can fit both the [HM]3ULCB > boards (actually also the new M3NULCB, I think). This being Kingfisher? I wrote this based on dts files in the tree. There's 2 combinations that I see: "shimafuji,kingfisher", "renesas,h3ulcb", "renesas,r8a7795" "shimafuji,kingfisher", "renesas,m3ulcb", "renesas,r8a7796" The schema allows 4 combinations (1 * 2 * 2). I have no idea if the other combinations are possible. If not, then we could rewrite this as 2 entries with 3 const values each. Rob