Hello,

Le 16/09/2016 12:08, Romain Perier a écrit :

The driver omap-rng has a lot of similarity with the IP block SafeXcel
IP-76. A lot of registers are the same and the way that the driver works
is very closed the description of the TRNG EIP76 in its datasheet.

This series refactorize the driver, add support for generating bigger
output random data and add a device variant for SafeXcel IP-76, found
in Armada 8K.

Romain Perier (8):
   dt-bindings: Add vendor prefix for INSIDE Secure
   dt-bindings: omap-rng: Document SafeXcel IP-76 device variant
   hwrng: omap - Switch to non-obsolete read API implementation
   hwrng: omap - Remove global definition of hwrng
   hwrng: omap - Add support for 128-bit output of data
   hwrng: omap - Don't prefix the probe message with OMAP
   hwrng: omap - Add device variant for SafeXcel IP-76 found in Armada 8K
   arm64: dts: marvell: add TRNG description for Armada 8K CP

  Documentation/devicetree/bindings/rng/omap_rng.txt |  14 +-
  .../devicetree/bindings/vendor-prefixes.txt        |   1 +
  .../boot/dts/marvell/armada-cp110-master.dtsi      |   8 +
  .../arm64/boot/dts/marvell/armada-cp110-slave.dtsi |   8 +
  drivers/char/hw_random/Kconfig                     |   2 +-
  drivers/char/hw_random/omap-rng.c                  | 162 ++++++++++++++++-----
  6 files changed, 152 insertions(+), 43 deletions(-)

If possible, I would like to get "Tested-by" tags by the omap guys 
before this set of patches is merged, to be sure that there are no 
regressions for the OMAP variant.

Thanks,
Regards,
-- 
Romain Perier, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com