From: Conor Dooley <conor@kernel.org>
To: Kamlesh Gurudasani <kamlesh@ti.com>
Cc: 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>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2 3/6] dt-bindings: crypto: Add Texas Instruments MCRC64
Date: Fri, 11 Aug 2023 16:36:54 +0100 [thread overview]
Message-ID: <20230811-imminent-fancied-89663c373ab5@spud> (raw)
In-Reply-To: <20230811-crestless-gratify-21c9bb422375@spud>
[-- Attachment #1: Type: text/plain, Size: 3532 bytes --]
On Fri, Aug 11, 2023 at 04:34:33PM +0100, Conor Dooley wrote:
> On Fri, Aug 11, 2023 at 12:58:50AM +0530, Kamlesh Gurudasani wrote:
> > Add binding for Texas Instruments MCRC64
> >
> > MCRC64 engine calculates 64-bit cyclic redundancy checks (CRC)
> > according to the ISO 3309 standard.
> >
> > The ISO 3309 64-bit CRC model parameters are as follows:
> > Generator Polynomial: x^64 + x^4 + x^3 + x + 1
> > Polynomial Value: 0x000000000000001B
> > Initial value: 0x0000000000000000
> > Reflected Input: False
> > Reflected Output: False
> > Xor Final: 0x0000000000000000
> >
> > Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
> > ---
> > Documentation/devicetree/bindings/crypto/ti,mcrc64.yaml | 47 +++++++++++++++++++++++++++++++++++++++++++++++
> > MAINTAINERS | 5 +++++
> > 2 files changed, 52 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/crypto/ti,mcrc64.yaml b/Documentation/devicetree/bindings/crypto/ti,mcrc64.yaml
> > new file mode 100644
> > index 000000000000..38bc7efebd68
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/crypto/ti,mcrc64.yaml
> > @@ -0,0 +1,47 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/crypto/ti,mcrc64.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Texas Instruments MCRC64
> > +
> > +description: The MCRC64 engine calculates 64-bit cyclic redundancy checks
>
> A newline after "description" please.
>
> > + (CRC) according to the ISO 3309 standard.
> > +
> > +maintainers:
> > + - Kamlesh Gurudasani <kamlesh@ti.com>
> > +
> > +properties:
> > + compatible:
> > + const: ti,am62-mcrc64
>
> Is the am62 an SoC or a family of SoCs? I googled a wee bit for am62 &
> there seems to be an am625 and an am623?
Or is it an am62p5, in which case the compatible should contain
ti,am62p5 I suppose. Sorry for my confusion here, its not really clear
me too since I've been seeing many different-but-similar product names
the last few days.
Thanks,
Conor.
>
> Otherwise, this looks good to me.
>
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + clocks:
> > + maxItems: 1
> > +
> > + power-domains:
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - clocks
> > + - power-domains
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/soc/ti,sci_pm_domain.h>
> > +
> > + crc@30300000 {
> > + compatible = "ti,am62-mcrc64";
> > + reg = <0x30300000 0x1000>;
> > + clocks = <&k3_clks 116 0>;
> > + power-domains = <&k3_pds 116 TI_SCI_PD_EXCLUSIVE>;
> > + };
> > +
> > +...
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 02a3192195af..66b51f43d196 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -21481,6 +21481,11 @@ S: Maintained
> > F: Documentation/devicetree/bindings/iio/adc/ti,lmp92064.yaml
> > F: drivers/iio/adc/ti-lmp92064.c
> >
> > +TI MEMORY CYCLIC REDUNDANCY CHECK (MCRC64) DRIVER
> > +M: Kamlesh Gurudasani <kamlesh@ti.com>
> > +S: Maintained
> > +F: Documentation/devicetree/bindings/crypto/ti,mcrc64.yaml
> > +
> > TI PCM3060 ASoC CODEC DRIVER
> > M: Kirill Marinushkin <kmarinushkin@birdec.com>
> > L: alsa-devel@alsa-project.org (moderated for non-subscribers)
> >
> > --
> > 2.34.1
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-11 15:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 19:28 [PATCH v2 0/6] Add support for Texas Instruments MCRC64 engine Kamlesh Gurudasani
2023-08-10 19:28 ` [PATCH v2 1/6] lib: add ISO 3309 model crc64 Kamlesh Gurudasani
2023-08-10 19:28 ` [PATCH v2 2/6] crypto: crc64 - add crc64-iso framework Kamlesh Gurudasani
2023-08-11 4:24 ` Eric Biggers
2023-08-11 6:40 ` [EXTERNAL] " Kamlesh Gurudasani
2023-08-12 2:55 ` Eric Biggers
2023-08-18 7:25 ` [EXTERNAL] " Kamlesh Gurudasani
2024-02-22 21:50 ` Elliott, Robert (Servers)
2024-02-29 8:45 ` Kamlesh Gurudasani
2023-08-10 19:28 ` [PATCH v2 3/6] dt-bindings: crypto: Add Texas Instruments MCRC64 Kamlesh Gurudasani
2023-08-11 15:34 ` Conor Dooley
2023-08-11 15:36 ` Conor Dooley [this message]
2024-05-27 8:25 ` [EXTERNAL] " Kamlesh Gurudasani
2024-05-27 8:33 ` Krzysztof Kozlowski
2024-05-27 10:11 ` Kamlesh Gurudasani
2024-05-29 5:13 ` Vignesh Raghavendra
2023-08-10 19:28 ` [PATCH v2 4/6] crypto: ti - add driver for MCRC64 engine Kamlesh Gurudasani
2023-08-10 19:28 ` [PATCH v2 5/6] arm64: dts: ti: k3-am62: Add dt node, cbass_main ranges for MCRC64 Kamlesh Gurudasani
2023-08-10 20:21 ` Nishanth Menon
2023-08-10 19:28 ` [PATCH v2 6/6] arm64: defconfig: enable TI MCRC64 module Kamlesh Gurudasani
2023-08-10 20:25 ` Nishanth Menon
2023-08-12 3:01 ` [PATCH v2 0/6] Add support for Texas Instruments MCRC64 engine Eric Biggers
2023-08-18 9:06 ` [EXTERNAL] " Kamlesh Gurudasani
2023-08-22 5:17 ` Eric Biggers
2023-08-30 11:51 ` [EXTERNAL] " Kamlesh Gurudasani
2023-09-20 6:53 ` Kamlesh Gurudasani
2023-10-03 6:07 ` Kamlesh Gurudasani
2023-08-30 13:48 ` Kamlesh Gurudasani
2023-08-30 14:46 ` Kamlesh Gurudasani
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=20230811-imminent-fancied-89663c373ab5@spud \
--to=conor@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kamlesh@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=will@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).