From: Om Prakash Singh <quic_omprsing@quicinc.com>
To: <neil.armstrong@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
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>, Vinod Koul <vkoul@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: crypto: qcom,prng: document SM8550
Date: Thu, 24 Aug 2023 05:02:29 +0530 [thread overview]
Message-ID: <d44be821-228b-4035-aa1e-c4f58db90422@quicinc.com> (raw)
In-Reply-To: <dd3d28f1-ff5e-49e6-a9f7-0ec9265017cc@linaro.org>
On 8/23/2023 1:25 PM, Neil Armstrong wrote:
> Hi,
>
> On 23/08/2023 02:10, Om Prakash Singh wrote:
>>
>>
>> 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
>
> I can send a proposal, but that means writing a new driver for this
> compatible in drivers/char/hw_random/ right ?
We can add hwrng support in same driver like
drivers/crypto/hisilicon/trng/trng.c
As Krzysztof is suggesting we need to have platform specific compatible
string, we can go with your change. for hwrng support I will send
separate patches.
>
> Neil
>
>>
>>>
>>>
>>> ?
>>>
>>> Konrad
>>
>> Thanks,
>> Om
>
next prev parent reply other threads:[~2023-08-23 23:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 14:11 [PATCH 0/2] arm64: qcom: sm8550: enable RNG Neil Armstrong
2023-08-22 14:11 ` [PATCH 1/2] dt-bindings: crypto: qcom,prng: document SM8550 Neil Armstrong
2023-08-22 14:14 ` Krzysztof Kozlowski
2023-08-22 14:28 ` Konrad Dybcio
2023-08-22 14:54 ` Om Prakash Singh
2023-08-22 15:28 ` Krzysztof Kozlowski
2023-08-22 16:04 ` Konrad Dybcio
2023-08-23 0:10 ` Om Prakash Singh
2023-08-23 7:55 ` Neil Armstrong
2023-08-23 23:32 ` Om Prakash Singh [this message]
2023-08-24 6:37 ` Krzysztof Kozlowski
2023-08-24 8:40 ` Konrad Dybcio
2023-08-24 8:46 ` neil.armstrong
2023-08-23 23:43 ` Om Prakash Singh
2023-08-22 14:11 ` [PATCH 2/2] arm64: dts: qcom: sm8550: Add PRNG Neil Armstrong
2023-08-23 23:47 ` Om Prakash Singh
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=d44be821-228b-4035-aa1e-c4f58db90422@quicinc.com \
--to=quic_omprsing@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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