From: Vinod <vkoul@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 3/3] hwrng: msm - Add support for prng v2
Date: Tue, 19 Jun 2018 09:36:30 +0530 [thread overview]
Message-ID: <20180619040630.GK25852@vkoul-mobl> (raw)
In-Reply-To: <152935345439.16708.16472364970375601294@swboyd.mtv.corp.google.com>
On 18-06-18, 13:24, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2018-06-18 11:21:23)
> > On Mon 18 Jun 07:12 PDT 2018, Vinod Koul wrote:
> >
> > > Qcom 8996 and later chips support prng v2 where we need to only
> > > implement .read callback for hwrng.
> > >
> >
> > The hardware still needs initialization, so I think you should expand
> > this to mention that the initialization is moved to secure world and
> > that's the reason why we only implement read.
> >
> > The question is what happens in projects with other security models.
>
> Can we still read the PRNG_CONFIG register to see if it's already been
> configured or not and then bail out if it isn't configured? That would
> be better as long as we the system doesn't blow up if non-secure mode
> tries to read the config register.
Unfortunately it did blow up for me when I tried it..
--
~Vinod
next prev parent reply other threads:[~2018-06-19 4:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 14:12 [PATCH 0/3]: hwrng: Add support for qcpm v2 hwrng Vinod Koul
2018-06-18 14:12 ` [PATCH 1/3] hwrng: msm - Move hwrng to a table Vinod Koul
2018-06-18 15:58 ` Stephen Boyd
2018-06-18 16:54 ` Vinod
2018-06-18 14:12 ` [PATCH 2/3] dt-bindings: rng: Add new compatible qcom,prng-v2 Vinod Koul
2018-06-18 14:12 ` [PATCH 3/3] hwrng: msm - Add support for prng v2 Vinod Koul
2018-06-18 18:21 ` Bjorn Andersson
2018-06-18 20:24 ` Stephen Boyd
2018-06-19 4:06 ` Vinod [this message]
2018-06-19 4:04 ` Vinod
2018-06-19 14:28 ` Herbert Xu
2018-06-20 5:32 ` Vinod
2018-06-20 14:37 ` Herbert Xu
2018-06-20 17:45 ` PrasannaKumar Muralidharan
2018-06-21 4:17 ` Vinod
2018-06-21 9:56 ` Stanimir Varbanov
2018-06-21 10:15 ` Herbert Xu
2018-06-21 11:27 ` Stanimir Varbanov
2018-06-21 11:53 ` Herbert Xu
2018-06-22 8:27 ` Stanimir Varbanov
2018-06-22 14:38 ` Herbert Xu
2018-06-22 14:48 ` Vinod
2018-06-22 14:50 ` Herbert Xu
[not found] ` <70ED61EB-BD3E-48D1-8B4D-D7835494C035@chronox.de>
2018-06-27 5:08 ` Vinod
2018-06-27 6:13 ` Stephan Mueller
2018-06-27 6:27 ` Vinod
2018-06-27 6:43 ` Stephan Mueller
2018-06-27 7:01 ` Vinod
2018-06-27 7:51 ` Stephan Mueller
2018-06-22 15:33 ` Stanimir Varbanov
2018-06-28 22:04 ` Timur Tabi
2018-06-29 8:37 ` Vinod
2018-07-01 6:27 ` Herbert Xu
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=20180619040630.GK25852@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=swboyd@chromium.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