Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <rafal@milecki.pl>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Antoine Tenart" <atenart@kernel.org>,
	linux-crypto@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: crypto: convert Inside Secure SafeXcel to the json-schema
Date: Thu, 16 Nov 2023 19:01:12 +0100	[thread overview]
Message-ID: <844c8a5387ca4c5847bf8cfa82b8164c@milecki.pl> (raw)
In-Reply-To: <3f9f31e9-ead3-438a-bbd9-818b98ba1b3b@linaro.org>

On 2023-11-16 15:42, Krzysztof Kozlowski wrote:
>> +properties:
>> +  compatible:
>> +    oneOf:
>> +      - const: inside-secure,safexcel-eip197b
>> +      - const: inside-secure,safexcel-eip197d
>> +      - const: inside-secure,safexcel-eip97ies
>> +      - const: inside-secure,safexcel-eip197
>> +        description: Equivalent of inside-secure,safexcel-eip197b
>> +        deprecated: true
>> +      - const: inside-secure,safexcel-eip97
>> +        description: Equivalent of inside-secure,safexcel-eip97ies
>> +        deprecated: true
> 
> Wait, some new entries appear here and commit msg said nothing about
> changes in the binding. Commit says it is pure conversion. You must
> document all changes made.

I may make many mistakes but not one like that. I am phobic to adding
new stuff silently. All those entries were documented in .txt.


>> +allOf:
>> +  - if:
>> +      properties:
>> +        clocks:
>> +          minItems: 2
>> +    then:
>> +      required:
>> +        - clock-names
> 
> Did you test that it actually works? Considering other patchset which
> you did not, I have doubts that this was...

Sorry, I really have bad experience with Python due its maze of
dependencies and unfriendly feedback. I just wasted half an hour
debugging error like:

Traceback (most recent call last):
   File "/home/rmilecki/.local/bin/dt-doc-validate", line 64, in <module>
     ret |= check_doc(f)
   File "/home/rmilecki/.local/bin/dt-doc-validate", line 32, in 
check_doc
     for error in sorted(dtsch.iter_errors(), key=lambda e: e.linecol):
   File 
"/home/rmilecki/.local/lib/python3.10/site-packages/dtschema/schema.py", 
line 132, in iter_errors
     self.annotate_error(scherr, meta_schema, scherr.schema_path)
   File 
"/home/rmilecki/.local/lib/python3.10/site-packages/dtschema/schema.py", 
line 111, in annotate_error
     schema = schema[p]
KeyError: 'type'

which turned out to be a result of some outdated examples files.

I tested that binding thought. Still after another look at that allOf I
found one more corner case to cover.

-- 
Rafał Miłecki

      reply	other threads:[~2023-11-16 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 13:06 [PATCH] dt-bindings: crypto: convert Inside Secure SafeXcel to the json-schema Rafał Miłecki
2023-11-16 14:42 ` Krzysztof Kozlowski
2023-11-16 18:01   ` Rafał Miłecki [this message]

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=844c8a5387ca4c5847bf8cfa82b8164c@milecki.pl \
    --to=rafal@milecki.pl \
    --cc=atenart@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=zajec5@gmail.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