From: Neal Liu <neal.liu@mediatek.com>
To: Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@kernel.org>
Cc: Neal Liu <neal.liu@mediatek.com>,
Crystal Guo <Crystal.Guo@mediatek.com>,
<linux-crypto@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <wsd_upstream@mediatek.com>
Subject: [PATCH v4 0/3] MediaTek Security random number generator support
Date: Mon, 24 Jun 2019 15:24:09 +0800 [thread overview]
Message-ID: <1561361052-13072-1-git-send-email-neal.liu@mediatek.com> (raw)
These patch series introduce a generic rng driver for Trustzone
based kernel driver which would like to communicate with ATF
SIP services.
Patch #1 initials SMC fid table for Mediatek SIP interfaces and
adds HWRNG related SMC call.
Patch #2..3 adds mtk-sec-rng kernel driver for Trustzone based SoCs.
For MediaTek SoCs on ARMv8 with TrustZone enabled, peripherals like
entropy sources is not accessible from normal world (linux) and
rather accessible from secure world (ATF/TEE) only. This driver aims
to provide a generic interface to ATF rng service.
changes since v1:
- rename mt67xx-rng to mtk-sec-rng since all MediaTek ARMv8 SoCs
can reuse this driver.
- refine coding style and unnecessary check.
changes since v2:
- remove unused comments.
- remove redundant variable.
changes since v3:
- add dt-bindings for MediaTek rng with TrustZone enabled
- revise HWRNG SMC call fid
Neal Liu (3):
soc: mediatek: add SMC fid table for SIP interface
dt-bindings: rng: add bindings for MediaTek ARMv8 SoCs
hwrng: add mtk-sec-rng driver
.../devicetree/bindings/rng/mtk-sec-rng.txt | 10 ++
drivers/char/hw_random/Kconfig | 16 +++
drivers/char/hw_random/Makefile | 1 +
drivers/char/hw_random/mtk-sec-rng.c | 97 +++++++++++++++++++
include/linux/soc/mediatek/mtk_sip_svc.h | 33 +++++++
5 files changed, 157 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rng/mtk-sec-rng.txt
create mode 100644 drivers/char/hw_random/mtk-sec-rng.c
create mode 100644 include/linux/soc/mediatek/mtk_sip_svc.h
--
2.18.0
next reply other threads:[~2019-06-24 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 7:24 Neal Liu [this message]
2019-06-24 7:24 ` [PATCH v4 1/3] soc: mediatek: add SMC fid table for SIP interface Neal Liu
2019-06-24 7:24 ` [PATCH v4 2/3] dt-bindings: rng: add bindings for MediaTek ARMv8 SoCs Neal Liu
2019-07-22 17:13 ` Rob Herring
2019-07-23 2:21 ` Neal Liu
2019-07-23 14:35 ` Rob Herring
2019-07-24 5:04 ` Neal Liu
2019-09-18 1:44 ` Neal Liu
2019-10-02 13:47 ` Neal Liu
2019-10-18 5:41 ` Neal Liu
2019-06-24 7:24 ` [PATCH v4 3/3] hwrng: add mtk-sec-rng driver Neal Liu
2019-07-22 9:50 ` [PATCH v4 0/3] MediaTek Security random number generator support Neal Liu
2019-08-02 1:35 ` Neal Liu
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=1561361052-13072-1-git-send-email-neal.liu@mediatek.com \
--to=neal.liu@mediatek.com \
--cc=Crystal.Guo@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mpm@selenic.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@kernel.org \
--cc=wsd_upstream@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).