linux-kernel - Re: [PATCH 1/2] dt-bindings: crypto: qcom,prng: document SM8550

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f61ef601-1561-45d7-8f4a-947458472668@quicinc.com>
Date:   Wed, 23 Aug 2023 05:40:57 +0530
From:   Om Prakash Singh <quic_omprsing@...cinc.com>
To:     Konrad Dybcio <konrad.dybcio@...aro.org>,
        Neil Armstrong <neil.armstrong@...aro.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        "David S. Miller" <davem@...emloft.net>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Vinod Koul <vkoul@...nel.org>
CC:     <linux-arm-msm@...r.kernel.org>, <linux-crypto@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: crypto: qcom,prng: document SM8550



On 8/22/2023 9:34 PM, Konrad Dybcio wrote:
> On 22.08.2023 16:54, Om Prakash Singh wrote:
>> PRNG Block on most of newer target from Qualcomm have some configuration where clock is configured by security firmware.
>>
>> Adding separate compatible string for each platform is overhead.
>>
>> We need to introduce common compatible string that can be used for all platforms with same configuration.
>>
>> I would suggest to use "qcom,rng-ee" for newer platform, dropping "p" also signifies it is not a Pseudo Random Number Generator.
> Please reply inline and don't top-post.
> 
> 
> Is this what you're trying to say?
> 
> 1. sort out the clock requirements for designs where Linux manages it
>     vs where the FW does so >
> 2. introduce a new compatible for SoCs implementing a TRNG
> 
> 3. for SoCs in 2., register the TRNG as a hwrng device

Yes to all

> 
> 
> ?
> 
> Konrad

Thanks,
Om