From: Drew Fustini <drew@pdp7.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
nvdimm@lists.linux.dev, Oliver O'Halloran <oohall@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v3] dt-bindings: pmem: Convert binding to YAML
Date: Mon, 9 Jun 2025 19:10:42 -0700 [thread overview]
Message-ID: <aEeUInXN6U40YSog@x1> (raw)
In-Reply-To: <6846f03e7b695_1a3419294dc@iweiny-mobl.notmuch>
On Mon, Jun 09, 2025 at 09:31:26AM -0500, Ira Weiny wrote:
> Dan Williams wrote:
> > [ add Ira ]
> >
> > Drew Fustini wrote:
> > > Convert the PMEM device tree binding from text to YAML. This will allow
> > > device trees with pmem-region nodes to pass dtbs_check.
> > >
> > > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > > Acked-by: Oliver O'Halloran <oohall@gmail.com>
> > > Signed-off-by: Drew Fustini <drew@pdp7.com>
> > > ---
> > > Dan/Dave/Vishal: does it make sense for this pmem binding patch to go
> > > through the nvdimm tree?
> >
> > Ira has been handling nvdimm pull requests as of late. Oliver's ack is
> > sufficient for me.
> >
> > Acked-by: Dan Williams <dan.j.williams@intel.com>
> >
> > @Ira do you have anything else pending?
> >
>
> I don't. I've never built the device tree make targets to test.
>
> The docs[1] say to run make dtbs_check but it is failing:
>
> $ make dtbs_check
> make[1]: *** No rule to make target 'dtbs_check'. Stop.
> make: *** [Makefile:248: __sub-make] Error 2
I believe this is because the ARCH is set to x86 and I don't believe
dtbs_check is valid for that. I work on riscv which does use device tree
so I use this command:
make ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- dtbs_check
>
>
> dt_binding_check fails too.
>
> $ make dt_binding_check
> SCHEMA Documentation/devicetree/bindings/processed-schema.json
> Traceback (most recent call last):
> File "/usr/bin/dt-mk-schema", line 8, in <module>
> sys.exit(main())
> ~~~~^^
> File "/usr/lib/python3.13/site-packages/dtschema/mk_schema.py", line 28, in main
> schemas = dtschema.DTValidator(args.schemas).schemas
> ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
> File "/usr/lib/python3.13/site-packages/dtschema/validator.py", line 373, in __init__
> self.make_property_type_cache()
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
> File "/usr/lib/python3.13/site-packages/dtschema/validator.py", line 460, in make_property_type_cache
> self.props, self.pat_props = get_prop_types(self.schemas)
> ~~~~~~~~~~~~~~^^^^^^^^^^^^^^
> File "/usr/lib/python3.13/site-packages/dtschema/validator.py", line 194, in get_prop_types
> del props[r'^[a-z][a-z0-9\-]*$']
> ~~~~~^^^^^^^^^^^^^^^^^^^^^^^
> KeyError: '^[a-z][a-z0-9\\-]*$'
> make[2]: *** [Documentation/devicetree/bindings/Makefile:63: Documentation/devicetree/bindings/processed-schema.json] Error 1
> make[2]: *** Deleting file 'Documentation/devicetree/bindings/processed-schema.json'
> make[1]: *** [/home/iweiny/dev/linux-nvdimm/Makefile:1522: dt_binding_schemas] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
>
> How do I test this?
dt_binding_check should work on x86. Maybe you don't have dtschema and
yamllint installed?
You should be able to install with:
pip3 install dtschema yamllint
And run the binding check with:
make dt_binding_check DT_SCHEMA_FILES=pmem-region.yaml
You should see the following output:
SCHEMA Documentation/devicetree/bindings/processed-schema.json
CHKDT ./Documentation/devicetree/bindings
LINT ./Documentation/devicetree/bindings
DTEX Documentation/devicetree/bindings/pmem/pmem-region.example.dts
DTC [C] Documentation/devicetree/bindings/pmem/pmem-region.example.dtb
Thanks,
Drew
next prev parent reply other threads:[~2025-06-10 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 18:11 [PATCH v3] dt-bindings: pmem: Convert binding to YAML Drew Fustini
2025-06-07 2:29 ` Dan Williams
2025-06-09 14:31 ` Ira Weiny
2025-06-10 2:10 ` Drew Fustini [this message]
2025-06-10 18:43 ` Drew Fustini
2025-06-10 22:05 ` Ira Weiny
2025-06-09 13:32 ` Rob Herring
2025-06-10 18:14 ` Drew Fustini
2025-06-11 14:33 ` Ira Weiny
2025-06-11 17:11 ` Drew Fustini
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=aEeUInXN6U40YSog@x1 \
--to=drew@pdp7.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=ira.weiny@intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=oohall@gmail.com \
--cc=robh@kernel.org \
--cc=vishal.l.verma@intel.com \
/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).