devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 0/5] Improve output type formatting
Date: Tue, 25 May 2021 20:03:30 -0500	[thread overview]
Message-ID: <20210526010335.860787-1-robh@kernel.org> (raw)

This series improves maintaining type information in the output of dtc 
from sources without any type annotations such as dtb format. It also 
makes the output formatting less dependent on the input source 
bracketing. As there's already a bunch of type information in the 
checks, we simply need to have the checks add markers.

This is needed in part to be able to run DT schema validation on dtb 
files. I also plan to use the schema files to provide type information 
for all the properties not covered by the dtc checks. Why not do this 
for all the properties? It's possible, but it wouldn't be possible with 
just pure schema. The phandle+args patterns with variable cells would 
need to recreate the same parsing code.

Rob

Rob Herring (5):
  yamltree: Remove marker ordering dependency
  checks: Add check_is_cell() for all phandle+arg properties
  checks: Drop interrupt_cells_is_cell check
  checks: Add markers on known properties
  dtc: Drop dts source restriction for yaml output

 checks.c           | 96 ++++++++++++++++++++++++++++++++++++----------
 dtc.c              |  2 -
 tests/run_tests.sh |  4 +-
 yamltree.c         | 16 ++++----
 4 files changed, 86 insertions(+), 32 deletions(-)

-- 
2.27.0


             reply	other threads:[~2021-05-26  1:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  1:03 Rob Herring [this message]
     [not found] ` <20210526010335.860787-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-05-26  1:03   ` [PATCH 1/5] yamltree: Remove marker ordering dependency Rob Herring
     [not found]     ` <20210526010335.860787-2-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-06-08  1:54       ` David Gibson
2021-05-26  1:03   ` [PATCH 2/5] checks: Add check_is_cell() for all phandle+arg properties Rob Herring
     [not found]     ` <20210526010335.860787-3-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-06-08  1:57       ` David Gibson
2021-06-08 14:45         ` Rob Herring
     [not found]           ` <CAL_JsqL5ks9G1_q+8LN_ceNjE-d40ri8G2BmnxnPCCa+UrqHgw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-15  6:02             ` David Gibson
2021-05-26  1:03   ` [PATCH 3/5] checks: Drop interrupt_cells_is_cell check Rob Herring
     [not found]     ` <20210526010335.860787-4-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-06-08  1:58       ` David Gibson
2021-05-26  1:03   ` [PATCH 4/5] checks: Add markers on known properties Rob Herring
     [not found]     ` <20210526010335.860787-5-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-06-08  2:25       ` David Gibson
2021-06-08 12:49         ` Rob Herring
     [not found]           ` <CAL_JsqKb-4ay9JNLUOetupxBKNpBsFNB-Ztc1ocbDSj_KxSWsg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-15  6:01             ` David Gibson
2021-06-15 14:25               ` Rob Herring
2021-05-26  1:03   ` [PATCH 5/5] dtc: Drop dts source restriction for yaml output Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210526010335.860787-1-robh@kernel.org \
    --to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).