From: Vinod <vkoul@kernel.org>
To: Timur Tabi <timur@codeaurora.org>
Cc: linux-crypto@vger.kernel.org, lkml <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, Stephen Boyd <swboyd@chromium.org>
Subject: Re: [PATCH v2 0/2] hwrng: Add support for qcpm v2 hwrng
Date: Fri, 22 Jun 2018 09:57:47 +0530 [thread overview]
Message-ID: <20180622042747.GH27187@vkoul-mobl> (raw)
In-Reply-To: <CAOZdJXUgYpLT=xMos4wKxMOTOZb8rV8is48YjGB8_9okZsuvhQ@mail.gmail.com>
On 21-06-18, 10:17, Timur Tabi wrote:
> On Tue, Jun 19, 2018 at 4:54 AM, Vinod Koul <vinod.koul@linaro.org> wrote:
> > This series adds support for newer version of hwrng as found in
> > Qualcomm SoCs. To do that add new v2 compatible string and driver_data
> > values for v2.
>
> It's amazing you're sending this now, because I also have a PRNG
> patchset that I'm sending out today that adds support for v2 chips on
> an ACPI platform.
>
> I'll send my patches as-is, and we'll just have to work to resolve the
> merge conflicts.
I have checked the series.
I am not sure I follow that this is v2 and you read CONFIG register.
Apart from that other changes look mostly okay with few nitpicks :)
But there is a bigger concern raised by Herbert on this not being a true
RNG and thus should be moved to crypto/
I have the changes ready for that, I will test them later today and
share with you, ACPI addition should be easy on that driver
> I will probably need you to test my patches as my last day at Qualcomm
> is the 26th.
Sad to hear that and good luck in your new adventure
--
~Vinod
next prev parent reply other threads:[~2018-06-22 4:27 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
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 [this message]
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=20180622042747.GH27187@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 \
--cc=timur@codeaurora.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