[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53fffe4b-d306-4707-aaad-cefa9beaa07c@kernel.org>
Date: Tue, 18 Jun 2024 08:33:33 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Sam Protsenko <semen.protsenko@...aro.org>,
Ćukasz Stelmach <l.stelmach@...sung.com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: Olivia Mackall <olivia@...enic.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Alim Akhtar <alim.akhtar@...sung.com>, linux-samsung-soc@...r.kernel.org,
linux-crypto@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/7] dt-bindings: rng: Add Exynos850 support to
exynos-trng
On 18/06/2024 02:37, Sam Protsenko wrote:
> The TRNG block in Exynos850 is pretty much the same as in Exynos5250,
> but there are two clocks that has to be controlled to make it work:
> 1. Functional (operating) clock: called ACLK in Exynos850, the same as
> "secss" clock in Exynos5250
> 2. Interface (bus) clock: called PCLK in Exynos850. It has to be
> enabled in order to access TRNG registers
>
> Document Exynos850 compatible and the related clock changes, and provide
> a corresponding example for Exynos850 TRNG node with ACLK and PCLK
> clocks.
>
...
> +
> + rng@...81400 {
> + compatible = "samsung,exynos850-trng";
> + reg = <0x12081400 0x100>;
> + clocks = <&cmu_core CLK_GOUT_SSS_ACLK>, <&cmu_core CLK_GOUT_SSS_PCLK>;
> + clock-names = "secss", "pclk";
> + };
No need for new example for difference in one property only.
Best regards,
Krzysztof
Powered by blists - more mailing lists