public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Marek Vasut <marex@denx.de>, David Airlie <airlied@linux.ie>
Cc: Rob Herring <robh@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: make dt_binding_check broken by drm & lvds-codec
Date: Wed, 22 Dec 2021 18:43:57 +0100	[thread overview]
Message-ID: <35c7df78-6e8a-b996-3df8-2c405bfcff81@gmail.com> (raw)

Hi,

I just noticed that "make dt_binding_check" doesn't work in linux-next:

   SCHEMA  Documentation/devicetree/bindings/processed-schema-examples.json
Traceback (most recent call last):
   File "/home/rmilecki/.local/bin/dt-mk-schema", line 38, in <module>
     schemas = dtschema.process_schemas(args.schemas, core_schema=(not args.useronly))
   File "/home/rmilecki/.local/lib/python3.6/site-packages/dtschema/lib.py", line 587, in process_schemas
     sch = process_schema(os.path.abspath(filename))
   File "/home/rmilecki/.local/lib/python3.6/site-packages/dtschema/lib.py", line 561, in process_schema
     schema = load_schema(filename)
   File "/home/rmilecki/.local/lib/python3.6/site-packages/dtschema/lib.py", line 126, in load_schema
     return do_load(os.path.join(schema_basedir, schema))
   File "/home/rmilecki/.local/lib/python3.6/site-packages/dtschema/lib.py", line 112, in do_load
     return yaml.load(tmp)
   File "/usr/lib/python3.6/site-packages/ruamel/yaml/main.py", line 343, in load
     return constructor.get_single_data()
   File "/usr/lib/python3.6/site-packages/ruamel/yaml/constructor.py", line 113, in get_single_data
     return self.construct_document(node)
   File "/usr/lib/python3.6/site-packages/ruamel/yaml/constructor.py", line 123, in construct_document
     for _dummy in generator:
   File "/usr/lib/python3.6/site-packages/ruamel/yaml/constructor.py", line 723, in construct_yaml_map
     value = self.construct_mapping(node)
   File "/usr/lib/python3.6/site-packages/ruamel/yaml/constructor.py", line 440, in construct_mapping
     return BaseConstructor.construct_mapping(self, node, deep=deep)
   File "/usr/lib/python3.6/site-packages/ruamel/yaml/constructor.py", line 257, in construct_mapping
     if self.check_mapping_key(node, key_node, mapping, key, value):
   File "/usr/lib/python3.6/site-packages/ruamel/yaml/constructor.py", line 295, in check_mapping_key
     raise DuplicateKeyError(*args)
ruamel.yaml.constructor.DuplicateKeyError: while constructing a mapping
   in "<unicode string>", line 4, column 1
found duplicate key "if" with value "{}" (original value: "{}")
   in "<unicode string>", line 113, column 1

It's caused by two commits:
ba3e86789eaf ("dt-bindings: display: bridge: lvds-codec: Document LVDS data mapping select")
d7df3948eb49 ("dt-bindings: display: bridge: lvds-codec: Document pixel data sampling edge select")

Both commits add "if" and "then" at YAML "root" level.

Can you take a look at that, please?

             reply	other threads:[~2021-12-22 17:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 17:43 Rafał Miłecki [this message]
2021-12-22 17:51 ` make dt_binding_check broken by drm & lvds-codec Marek Vasut

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=35c7df78-6e8a-b996-3df8-2c405bfcff81@gmail.com \
    --to=zajec5@gmail.com \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=robh@kernel.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