Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Alexey Romanov <avromanov@sberdevices.ru>
Cc: narmstrong@baylibre.com, neil.armstrong@linaro.org,
	olivia@selenic.com, herbert@gondor.apana.org.au,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, khilman@baylibre.com, jbrunet@baylibre.com,
	martin.blumenstingl@googlemail.com, f.fainelli@gmail.com,
	hkallweit1@gmail.com, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-crypto@vger.kernel.org,
	kernel@sberdevices.ru
Subject: Re: [PATCH v1 2/3] dt-bindings: rng: meson: add meson-rng-s4 compatible
Date: Tue, 25 Jul 2023 19:13:59 +0100	[thread overview]
Message-ID: <20230725-transport-pension-533b598260d0@spud> (raw)
In-Reply-To: <20230725141252.98848-3-avromanov@sberdevices.ru>

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

On Tue, Jul 25, 2023 at 05:12:51PM +0300, Alexey Romanov wrote:
> Now the driver has a separate algo for S4 SoC.
> 
> Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
> ---
>  Documentation/devicetree/bindings/rng/amlogic,meson-rng.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/rng/amlogic,meson-rng.yaml b/Documentation/devicetree/bindings/rng/amlogic,meson-rng.yaml
> index 457a6e43d810..6f51506c0f65 100644
> --- a/Documentation/devicetree/bindings/rng/amlogic,meson-rng.yaml
> +++ b/Documentation/devicetree/bindings/rng/amlogic,meson-rng.yaml
> @@ -14,6 +14,7 @@ properties:
>    compatible:
>      enum:
>        - amlogic,meson-rng
> +      - amlogic,meson-rng-s4

Usually, the "s4" would come before the peripheral's name, as s4 is the
name of the SoC.

>  
>    reg:
>      maxItems: 1
> -- 
> 2.38.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-07-25 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 14:12 [PATCH v1 0/3] Meson S4 HW RNG Support Alexey Romanov
2023-07-25 14:12 ` [PATCH v1 1/3] drivers: rng: add check status bit feature Alexey Romanov
2023-07-25 19:59   ` Martin Kaiser
2023-07-26  7:52     ` Alexey Romanov
2023-07-26 11:54       ` Martin Kaiser
2023-07-27 19:14   ` Martin Blumenstingl
2023-07-25 14:12 ` [PATCH v1 2/3] dt-bindings: rng: meson: add meson-rng-s4 compatible Alexey Romanov
2023-07-25 18:13   ` Conor Dooley [this message]
2023-07-25 14:12 ` [PATCH v1 3/3] arch/arm64: dts: meson-s4: add hwrng node Alexey Romanov

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=20230725-transport-pension-533b598260d0@spud \
    --to=conor@kernel.org \
    --cc=avromanov@sberdevices.ru \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=hkallweit1@gmail.com \
    --cc=jbrunet@baylibre.com \
    --cc=kernel@sberdevices.ru \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=narmstrong@baylibre.com \
    --cc=neil.armstrong@linaro.org \
    --cc=olivia@selenic.com \
    --cc=robh+dt@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