From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>
Cc: devicetree@vger.kernel.org, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, robh@kernel.org,
Ruud.Derwig@synopsys.com, manjunath.hadli@vayavyalabs.com,
bhoomikak@vayavyalabs.com
Subject: Re: [PATCH v9 7/7] dt-bindings: crypto: Document support for SPAcc
Date: Tue, 1 Oct 2024 08:15:13 +0200 [thread overview]
Message-ID: <5f3969cb-268e-4383-a6b9-51c169f2e94a@kernel.org> (raw)
In-Reply-To: <CALxtO0=7+8sX5LXK0XLjrCJH7P3s9FkKWPGVjp2q_dgq1q2M3g@mail.gmail.com>
On 01/10/2024 04:57, Pavitrakumar Managutte wrote:
> Hi Krzysztof,
> Thanks for the quick review and I do really appreciate everybody's time here.
> If something got missed, it's just because of the exhaustive
> hardware and the SystemC Model testing.
> We make minimal/incremental changes and run things in debug mode
> which takes a lot of time,
> since this is a large code base. Never ignored anything till date.
> Every single comment has been and will be addressed. We will work
> on code quality as per your inputs.
No, it was not addressed.
Do you want proofs? Look:
1. Drop contains. The list of compatible strings and order must be defined.
Not addressed at all.
2. crypto@40000000
Ignored completely
3. Generally drivers aren't limited to some number of instances (except...
Also ignored completely
and more..
>
> Warm regards,
> PK
>
>
> On Mon, Sep 30, 2024 at 6:50 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On 30/09/2024 11:30, Pavitrakumar M wrote:
>>> Add DT bindings related to the SPAcc driver for Documentation.
>>> DWC Synopsys Security Protocol Accelerator(SPAcc) Hardware Crypto
>>> Engine is a crypto IP designed by Synopsys.
>>>
>>> Co-developed-by: Bhoomika Kadabi <bhoomikak@vayavyalabs.com>
>>> Signed-off-by: Bhoomika Kadabi <bhoomikak@vayavyalabs.com>
>>> Co-developed-by: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>
>>> Signed-off-by: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>
>>> Acked-by: Ruud Derwig <Ruud.Derwig@synopsys.com>
>>> ---
>>> .../bindings/crypto/snps,dwc-spacc.yaml | 71 +++++++++++++++++++
>>> 1 file changed, 71 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/crypto/snps,dwc-spacc.yaml
>>
>> Bindings come before users, so please re-order your patches.
>
> PK: Will re-order
>>
>>
>>>
>>> diff --git a/Documentation/devicetree/bindings/crypto/snps,dwc-spacc.yaml b/Documentation/devicetree/bindings/crypto/snps,dwc-spacc.yaml
>>> new file mode 100644
>>> index 000000000000..6b94d0aa7280
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/crypto/snps,dwc-spacc.yaml
>>> @@ -0,0 +1,71 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/crypto/snps,dwc-spacc.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Synopsys DesignWare Security Protocol Accelerator(SPAcc) Crypto Engine
>>> +
>>> +maintainers:
>>> + - Ruud Derwig <Ruud.Derwig@synopsys.com>
>>> +
>>> +description:
>>> + DWC Synopsys Security Protocol Accelerator(SPAcc) Hardware Crypto Engine is
>>> + a crypto IP designed by Synopsys, that can accelerate cryptographic
>>> + operations.
>>> +
>>> +properties:
>>> + compatible:
>>> + contains:
>>
>> Nope, you cannot have contains. From where did you get it? Please use
>> existing, recent bindings as starting point or just use exampl-eschema.
>
> PK: Will fix that.
>>
>>
>> Eh, you already got this comment and just ignored it.
>
> PK: It got missed, never ignored. Too valuable to ignore comments from demigods.
>>
>>
>> You ignored all other comments as well. This is quite disappointing to
>> ask us to do the same review over and over.
>
> PK: That never was the intent nor the impression I wanted to make.
> Appreciate everybody's time here.
Then why do you ignore review?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-01 6:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 9:30 [PATCH v9 0/7] Add SPAcc Crypto Driver Pavitrakumar M
2024-09-30 9:30 ` [PATCH v9 1/7] Add SPAcc Skcipher support Pavitrakumar M
2024-09-30 13:34 ` Krzysztof Kozlowski
2024-09-30 9:30 ` [PATCH v9 2/7] Add SPAcc AUTODETECT Support Pavitrakumar M
2024-09-30 9:30 ` [PATCH v9 3/7] Add SPAcc ahash support Pavitrakumar M
2024-09-30 9:30 ` [PATCH v9 4/7] Add SPAcc AEAD support Pavitrakumar M
2024-09-30 13:25 ` Krzysztof Kozlowski
2024-09-30 9:30 ` [PATCH v9 5/7] Add SPAcc Kconfig and Makefile Pavitrakumar M
2024-09-30 13:23 ` Krzysztof Kozlowski
2024-09-30 9:30 ` [PATCH v9 6/7] Add SPAcc compilation in crypto Pavitrakumar M
2024-09-30 13:22 ` Krzysztof Kozlowski
2024-09-30 9:30 ` [PATCH v9 7/7] dt-bindings: crypto: Document support for SPAcc Pavitrakumar M
2024-09-30 13:20 ` Krzysztof Kozlowski
2024-10-01 2:57 ` Pavitrakumar Managutte
2024-10-01 6:15 ` Krzysztof Kozlowski [this message]
2024-10-01 6:32 ` Krzysztof Kozlowski
2024-10-01 7:23 ` Pavitrakumar Managutte
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=5f3969cb-268e-4383-a6b9-51c169f2e94a@kernel.org \
--to=krzk@kernel.org \
--cc=Ruud.Derwig@synopsys.com \
--cc=bhoomikak@vayavyalabs.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=manjunath.hadli@vayavyalabs.com \
--cc=pavitrakumarm@vayavyalabs.com \
--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;
as well as URLs for NNTP newsgroup(s).