CVS log for src/sys/arch/arm/dts/rk3399-crypto.dtsi

Up to [cvs.NetBSD.org] / src / sys / arch / arm / dts

Request diff between arbitrary revisions

Default branch: MAIN

Revision 1.1.2.2 / (download) - annotate - [select for diffs], Mon May 18 18:54:30 2020 UTC (3 years ago) by martin
Branch: netbsd-9
CVS Tags: netbsd-9-3-RELEASE, netbsd-9-2-RELEASE, netbsd-9-1-RELEASE
Changes since 1.1.2.1: +41 -0 lines
Diff to previous 1.1.2.1 (colored) to branchpoint 1.1 (colored)

Pull up following revision(s) (requested by riastradh in ticket #913):

	sys/arch/arm/dts/rk3399-crypto.dtsi: revision 1.1
	sys/arch/arm/rockchip/rk_v1crypto.c: revision 1.1
	sys/arch/arm/rockchip/rk_v1crypto.c: revision 1.2 (plus patch)
	sys/arch/arm/rockchip/rk_v1crypto.h: revision 1.1
	sys/arch/arm/dts/rk3399-pinebook-pro.dts: revision 1.3
	sys/arch/arm/rockchip/rk3399_cru.c: revision 1.20
	sys/arch/evbarm/conf/GENERIC64: revision 1.158
	sys/arch/arm/dts/rk3399-rockpro64.dts: revision 1.11
	sys/arch/arm/rockchip/files.rockchip: revision 1.24

Rockchip crypto engine RNG driver.

As found on the rk3288 and rk3399.  This driver only supports the
TRNG, not the rest of the crypto engine, although it uses the AES unit
to do a self-test at attach time to verify that the engine works.
There seem to be two versions of the Rockchip crypto engine, v1 and
v2; this one is for v1.  Can't name a driver `rkcryptov1' so we'll
clumsily call it `rkv1crypto' instead to leave room for `rkv2crypto'
later on.

The crypto binding derived from the Rockchip BSP Linux kernel, in the
location it appears on the rk3399, is in rk3399-crypto.dtsi, since
there doesn't seem to be a better place to put it at the moment among
this twisty maze of inclusions, all different.

Use rnd_add_data_sync from the callback.

(Doesn't make a difference in HEAD but this is the stated API
contract and it matters if we want to pull this up.)

Prime the pool on attach.

Revision 1.1.2.1, Sun May 17 19:57:25 2020 UTC (3 years ago) by martin
Branch: netbsd-9
Changes since 1.1: +0 -41 lines
FILE REMOVED

file rk3399-crypto.dtsi was added on branch netbsd-9 on 2020-05-18 18:54:30 +0000

Revision 1.1 / (download) - annotate - [select for diffs], Sun May 17 19:57:25 2020 UTC (3 years ago) by riastradh
Branch: MAIN
CVS Tags: thorpej-i2c-spi-conf2-base, thorpej-i2c-spi-conf2, thorpej-i2c-spi-conf-base, thorpej-i2c-spi-conf, thorpej-futex2-base, thorpej-futex2, thorpej-futex-base, thorpej-futex, thorpej-cfargs2-base, thorpej-cfargs2, thorpej-cfargs-base, thorpej-cfargs, netbsd-10-base, netbsd-10, cjep_sun2x-base1, cjep_sun2x-base, cjep_sun2x, cjep_staticlib_x-base1, cjep_staticlib_x-base, cjep_staticlib_x, bouyer-sunxi-drm-base, bouyer-sunxi-drm, HEAD
Branch point for: netbsd-9

Rockchip crypto engine RNG driver.

As found on the rk3288 and rk3399.  This driver only supports the
TRNG, not the rest of the crypto engine, although it uses the AES unit
to do a self-test at attach time to verify that the engine works.

There seem to be two versions of the Rockchip crypto engine, v1 and
v2; this one is for v1.  Can't name a driver `rkcryptov1' so we'll
clumsily call it `rkv1crypto' instead to leave room for `rkv2crypto'
later on.

The crypto binding derived from the Rockchip BSP Linux kernel, in the
location it appears on the rk3399, is in rk3399-crypto.dtsi, since
there doesn't seem to be a better place to put it at the moment among
this twisty maze of inclusions, all different.

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.