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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6A12C433FE for ; Fri, 4 Mar 2022 14:07:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239797AbiCDOIO (ORCPT ); Fri, 4 Mar 2022 09:08:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52176 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239803AbiCDOIM (ORCPT ); Fri, 4 Mar 2022 09:08:12 -0500 Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C06331B98B4; Fri, 4 Mar 2022 06:07:24 -0800 (PST) Received: by mail-oi1-f176.google.com with SMTP id ay7so7899410oib.8; Fri, 04 Mar 2022 06:07:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Ri3M9rEvbqOZtQYvLCw0kYxpmzURzsEZbFbaOsupS2s=; b=0CxaWSHe0/k/VmyK4TfUy//1oCz9pXmtX26BVk067+I3szWXPdkFvG8xknFlp9CloP lVyU2uFWyoCGdUz6Abrs/gbNOJhecef/bsR0EO1YT/QeyAVJiPfbIzLqiqD35AuV+mOw /axcDvQh6AK6jhzr0sxOGtSFUiHAEgpYYT7JUmbrCfUW6B+9CpU3hpl9i1NN0WctSEMl tlSWLemJIkS0ZxFdyI4CEaNDADjx+6uxjqBOuhhWQcGKkWpWeDYZBQgXuCzGcDPXkpCP ppadtwHcWatQx+HKQAKJ2dDxifA357khg+EfG2Z+DirA3hdnPrZ4CUdY9zLO922acopH qoYw== X-Gm-Message-State: AOAM533Q3NOC+OPbgAbg30pn+6Ep5t7ofuV9pJb69JH23MBLI8m0gkjO lsdJD0S5ikQSalFYePzo/A== X-Google-Smtp-Source: ABdhPJyci6UbkOLrwsWccGvun1sxcDyW/kMEWbKggLvHH1s6vVcgxC1dz4Bb6r88ow5hTuC9ncAQmQ== X-Received: by 2002:a05:6808:d52:b0:2d7:4e5a:6edb with SMTP id w18-20020a0568080d5200b002d74e5a6edbmr9428953oik.131.1646402843673; Fri, 04 Mar 2022 06:07:23 -0800 (PST) Received: from robh.at.kernel.org (66-90-148-213.dyn.grandenetworks.net. [66.90.148.213]) by smtp.gmail.com with ESMTPSA id a27-20020a4ae93b000000b0031be7c7d2d3sm2446568ooe.0.2022.03.04.06.07.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 04 Mar 2022 06:07:23 -0800 (PST) Received: (nullmailer pid 3842339 invoked by uid 1000); Fri, 04 Mar 2022 14:07:21 -0000 Date: Fri, 4 Mar 2022 08:07:21 -0600 From: Rob Herring To: Laurent Pinchart Cc: Masahiro Yamada , Krzysztof Kozlowski , Michal Marek , Nick Desaulniers , Frank Rowand , Geert Uytterhoeven , Maxime Ripard , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-kbuild@vger.kernel.org Subject: Re: [PATCH 2/2] dt-bindings: kbuild: Use DTB files for validation Message-ID: References: <20220303224237.2497570-1-robh@kernel.org> <20220303224237.2497570-3-robh@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Fri, Mar 04, 2022 at 01:55:59PM +0200, Laurent Pinchart wrote: > Hi Rob, > > Thank you for the patch. > > On Thu, Mar 03, 2022 at 04:42:37PM -0600, Rob Herring wrote: > > Switch the DT validation to use DTB files directly instead of a DTS to > > YAML conversion. > > > > The original motivation for supporting validation on DTB files was to > > enable running validation on a running system (e.g. 'dt-validate > > /sys/firmware/fdt') or other cases where the original source DTS is not > > available. > > > > The YAML format was not without issues. Using DTBs with the schema type > > information solves some of those problems. The YAML format relies on the > > DTS source level information including bracketing of properties, size > > directives, and phandle tags all of which are lost in a DTB file. While > > standardizing the bracketing is a good thing, it does cause a lot of > > extra warnings and churn to fix them. > > It does indeed, but it's a bit sad to let that feature go :-S I agree, but I think that checking is better served with a DTS linter. Rob