From: Vinod <vkoul@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: 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 v2 2/2] hwrng: msm - Add support for prng v2
Date: Wed, 20 Jun 2018 19:07:25 +0530 [thread overview]
Message-ID: <20180620133725.GB27187@vkoul-mobl> (raw)
In-Reply-To: <152947431955.16708.15247307054260887941@swboyd.mtv.corp.google.com>
On 19-06-18, 22:58, Stephen Boyd wrote:
> Quoting Vinod Koul (2018-06-19 02:54:30)
> > Qcom 8996 and later chips support prng v2 which requires to
> > implement only .read callback for hwrng.
> >
> > This version of chip has multiple Execution Environments (EE) and
> > secure world is typically responsible for configuring the prng.
>
> Sometimes secure world is not configuring the rng though. I prefer we
> have a DT flag for this to indicate if secure world has configured it or
> not and then skip the init logic when the bool property is present in
> DT. Then the DT property can be set on firmwares that are making things
> blow up when we try to read the 'configured' register. I'd also file a
> bug to qcom to tell them to unlock that config register for reads so
> that things can work simpler, but who knows how that will work out.
I dont feel that would be required. See below..
> It really sounds like the hardware isn't actually different, just the
> firmware has decided to be more strict about making reads fail now.
So in this case base hw block seems similar but consists of multiple
Execution Environment (EEs) and all of these contain only data
registers. Only secure environment has configuration. Each one has its
own register space.
In a case where we dont have secure world, we can point to secure
environment with v1 ops, so driver shall configure and run.
Thanks
--
~Vinod
next prev parent reply other threads:[~2018-06-20 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 9:54 [PATCH v2 0/2] hwrng: Add support for qcpm v2 hwrng Vinod Koul
2018-06-19 9:54 ` [PATCH v2 1/2] dt-bindings: rng: Add new compatible qcom,prng-v2 Vinod Koul
2018-06-25 19:06 ` Rob Herring
2018-06-26 15:27 ` Vinod
2018-06-19 9:54 ` [PATCH v2 2/2] hwrng: msm - Add support for prng v2 Vinod Koul
2018-06-19 12:11 ` Stanimir Varbanov
2018-06-19 12:31 ` Vinod
2018-06-19 14:30 ` Herbert Xu
2018-06-20 5:58 ` Stephen Boyd
2018-06-20 13:37 ` Vinod [this message]
2018-06-22 1:22 ` Stephen Boyd
2018-06-21 15:17 ` [PATCH v2 0/2] hwrng: Add support for qcpm v2 hwrng Timur Tabi
2018-06-22 4:27 ` Vinod
2018-06-22 4:30 ` Timur Tabi
2018-06-22 4:50 ` Vinod
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=20180620133725.GB27187@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=arnd@arndb.de \
--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