From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 33F0AC282C0 for ; Wed, 23 Jan 2019 15:34:55 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 711902184C for ; Wed, 23 Jan 2019 15:34:54 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 711902184C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 43l8VM5dnRzDqMC for ; Thu, 24 Jan 2019 02:34:51 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=209.85.222.67; helo=mail-ua1-f67.google.com; envelope-from=geert.uytterhoeven@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Received: from mail-ua1-f67.google.com (mail-ua1-f67.google.com [209.85.222.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 43l8Sh6nLyzDqDm for ; Thu, 24 Jan 2019 02:33:24 +1100 (AEDT) Received: by mail-ua1-f67.google.com with SMTP id z11so835561uaa.10 for ; Wed, 23 Jan 2019 07:33:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZSHkQMfLLdepeDCVQenJz5d2pdB1BZBSB6tWTabXfX0=; b=ViuDSinTFuvSbFq9+P0ZkxdoTl/GUSMAuF0pbINljUz3oVUnm2HkO+oeOIDcL99U/7 B0+3ipJd6WL8gYA1yNkjWWoT9EHuIxFK8IV8UXrtCHT/j9wHfPTp9P7c7a/Fmfxy+JY9 nTy5LPjniJ6InG9aJqU2c8vlkO2yad2Amn5jSqXI8HjyduQm9w5c0MfV6WJKclj4DGUf b2fFcrcKKHuuSyfsdm4SjedKDABRLzomQUYHtPcH0ShloUwJJdGZ9dw1sct8j0Yfj351 YHs6gDhI6TuF4vXRsYeVjJd1ZOCmrBQCsl7A+QopRORLxcNsxmkndKsRL/4yAhM9kczy ztRQ== X-Gm-Message-State: AJcUukf7+ZZRPWvVoa+g9Uwi+HWCgR0CULARH6y9N7KokXya22xsMSqw lsEwB81LBtJt55iVgDFcloNUE+yonKuERZkolbY= X-Google-Smtp-Source: ALg8bN411XN+/POecIOHkbERwk16PlKxGOoUzZRR+A06ByaQtAch2faN4J7KsCjNSKQqXO/AlB0D4mENUIQ4ibIYn7I= X-Received: by 2002:ab0:1393:: with SMTP id m19mr976671uae.75.1548257602011; Wed, 23 Jan 2019 07:33:22 -0800 (PST) MIME-Version: 1.0 References: <20181211202406.27721-1-robh@kernel.org> In-Reply-To: <20181211202406.27721-1-robh@kernel.org> From: Geert Uytterhoeven Date: Wed, 23 Jan 2019 16:33:10 +0100 Message-ID: Subject: Re: [PATCH v4] kbuild: Add support for DT binding schema checks To: Rob Herring Content-Type: text/plain; charset="UTF-8" X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Kumar Gala , arm-soc , Sean Hudson , Jonathan Corbet , linuxppc-dev , "open list:DOCUMENTATION" , Linux Kernel Mailing List , linux-kbuild , Masahiro Yamada , Grant Likely , Michal Marek , Frank Rowand , Linux ARM Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Hi Rob, On Tue, Dec 11, 2018 at 9:24 PM Rob Herring wrote: > This adds the build infrastructure for checking DT binding schema > documents and validating dts files using the binding schema. > > Check DT binding schema documents: > make dt_binding_check > > Build dts files and check using DT binding schema: > make dtbs_check > > Optionally, DT_SCHEMA_FILES can be passed in with a schema file(s) to > use for validation. This makes it easier to find and fix errors > generated by a specific schema. > > Currently, the validation targets are separate from a normal build to > avoid a hard dependency on the external DT schema project and because > there are lots of warnings generated. Thanks, I'm giving this a try, and get errors like: DTC arch/arm/boot/dts/emev2-kzm9d.dt.yaml FATAL ERROR: No markers present in property 'cpu0' value and DTC arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dt.yaml FATAL ERROR: No markers present in property 'audio_clk_a' value Do you have a clue? Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds