1. 24 8月, 2015 2 次提交
  2. 18 8月, 2015 1 次提交
    • H
      crypto: caam - add support for LS1021A · 6c3af955
      Horia Geant? 提交于
      LS1021A is a QorIQ SoC having little endian CAAM.
      
      There are a few differences b/w QorIQ and i.MX from CAAM perspective:
      
      1. i.MX platforms are somewhat special wrt. 64-bit registers:
      -big endian format at 64-bit level: MSW at address+0 and LSW at address+4
      -little endian format at 32-bit level (within MSW and LSW)
      and thus need special handling.
      
      2. No CCM (clock controller module) for QorIQ.
      No CAAM clocks to enable / disable.
      
      A new Kconfig option - CRYPTO_DEV_FSL_CAAM_LE - is added to indicate
      CAAM is little endian (*). It is hidden from the user (to avoid
      misconfiguration); when adding support for a new platform with LE CAAM,
      either the Kconfig needs to be updated or the corresponding defconfig
      needs to indicate that CAAM is LE.
      (*) Using a DT property to provide CAAM endianness would not allow
      for the ifdeffery.
      
      In order to keep changes to a minimum, the following changes
      are postponed:
      -endianness fix of the last word in the S/G (rsvd2, bpid, offset),
      fields are always 0 anyway;
      -S/G format fix for i.MX7 (yes, i.MX7 support was not added yet,
      but still...)
      Signed-off-by: NHoria Geant? <horia.geanta@freescale.com>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      6c3af955
  3. 13 8月, 2015 1 次提交
  4. 10 8月, 2015 2 次提交
  5. 20 7月, 2015 3 次提交
  6. 16 6月, 2015 1 次提交
  7. 26 1月, 2015 1 次提交
  8. 20 10月, 2014 1 次提交
  9. 15 9月, 2014 1 次提交
  10. 25 8月, 2014 3 次提交
    • A
      crypto: caam - enable raw data instead of von Neumann data · e5ffbfc1
      Alex Porosanu 提交于
      The sampling of the oscillator can be done in multiple modes for
      generating the entropy value. By default, this is set to von
      Neumann. This patch changes the sampling to raw data, since it
      has been discovered that the generated entropy has a better
      'quality'.
      Signed-off-by: NAlex Porosanu <alexandru.porosanu@freescale.com>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      e5ffbfc1
    • A
      crypto: caam - change starting entropy delay value · eeaa1724
      Alex Porosanu 提交于
      The entropy delay (the length in system clocks of each
      entropy sample) for the RNG4 block of CAAM is dependent
      on the frequency of the SoC. By elaborate methods, it
      has been determined that a good starting value for all
      platforms integrating the CAAM IP is 3200. Using a
      higher value has additional benefit of  speeding up
      the process of instantiating the RNG, since the entropy
      delay will be increased and instantiation of the RNG
      state handles will be reattempted by the driver. If the
      starting value is low, for certain platforms, this can
      lead to a quite lengthy process.
      This patch changes the starting value of the length of
      the entropy sample to 3200 system clocks.
      In addition to this change, the attempted entropy delay
      values are now printed on the console upon initialization
      of the RNG block.
      While here, a safeguard for yielding the processor was
      added for ensuring that in very adverse cases,
      the CPU isn't hogged by the instantiation loop.
      Signed-off-by: NAlex Porosanu <alexandru.porosanu@freescale.com>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      eeaa1724
    • A
      crypto: caam - disable RNG oscillator maximum frequency check · b061f3fe
      Alex Porosanu 提交于
      The rtfrqmax & rtfrqmin set the bounds of the expected frequency of the
      oscillator, when SEC runs at its maximum frequency. For certain platforms
      (f.i. T2080), the oscillator is very fast and thus if the SEC runs at
      a lower than normal frequency, the ring oscillator is incorrectly detected
      as being out of bounds.
      
      This patch effectively disables the maximum frequency check, by setting a
      high enough maximum allowable frequency for the oscillator. The reasoning
      behind this is that usually a broken oscillator will run too slow
      (i.e. not run at all) rather than run too fast.
      Signed-off-by: NAlex Porosanu <alexandru.porosanu@freescale.com>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      b061f3fe
  11. 23 7月, 2014 2 次提交
  12. 08 7月, 2014 1 次提交
  13. 25 6月, 2014 2 次提交
  14. 20 6月, 2014 1 次提交
    • H
      crypto: caam - Introduce the use of the managed version of kzalloc · 4776d381
      Himangi Saraogi 提交于
      This patch moves data allocated using kzalloc to managed data allocated
      using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
      functions.  Also, linux/device.h is added to make sure the devm_*()
      routine declarations are unambiguously available. Earlier, in the probe
      function ctrlpriv was leaked on the failure of ctrl = of_iomap(nprop, 0);
      as well as on the failure of ctrlpriv->jrpdev = kzalloc(...); . These
      two bugs have been fixed by the patch.
      
      The following Coccinelle semantic patch was used for making the change:
      
      identifier p, probefn, removefn;
      @@
      struct platform_driver p = {
        .probe = probefn,
        .remove = removefn,
      };
      
      @prb@
      identifier platform.probefn, pdev;
      expression e, e1, e2;
      @@
      probefn(struct platform_device *pdev, ...) {
        <+...
      - e = kzalloc(e1, e2)
      + e = devm_kzalloc(&pdev->dev, e1, e2)
        ...
      ?-kfree(e);
        ...+>
      }
      
      @rem depends on prb@
      identifier platform.removefn;
      expression e;
      @@
      removefn(...) {
        <...
      - kfree(e);
        ...>
      }
      Signed-off-by: NHimangi Saraogi <himangi774@gmail.com>
      Acked-by: NJulia Lawall <julia.lawall@lip6.fr>
      Reviewed-by: NMarek Vasut <marex@denx.de>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      4776d381
  15. 09 2月, 2014 2 次提交
  16. 30 10月, 2013 1 次提交
  17. 24 10月, 2013 1 次提交
  18. 10 10月, 2013 1 次提交
  19. 13 9月, 2013 6 次提交
  20. 01 8月, 2013 2 次提交
  21. 14 5月, 2013 1 次提交
  22. 22 3月, 2013 1 次提交
  23. 18 3月, 2013 1 次提交
  24. 04 1月, 2013 1 次提交
    • G
      Drivers: crypto: remove __dev* attributes. · 49cfe4db
      Greg Kroah-Hartman 提交于
      CONFIG_HOTPLUG is going away as an option.  As a result, the __dev*
      markings need to be removed.
      
      This change removes the use of __devinit, __devexit_p, __devinitdata,
      and __devexit from these drivers.
      
      Based on patches originally written by Bill Pemberton, but redone by me
      in order to handle some of the coding style issues better, by hand.
      
      Cc: Bill Pemberton <wfp5p@virginia.edu>
      Cc: Herbert Xu <herbert@gondor.apana.org.au>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Kent Yoder <key@linux.vnet.ibm.com>
      Cc: Jamie Iles <jamie@jamieiles.com>
      Cc: Kim Phillips <kim.phillips@freescale.com>
      Cc: Shengzhou Liu <Shengzhou.Liu@freescale.com>
      Cc: Alex Porosanu <alexandru.porosanu@freescale.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      49cfe4db
  25. 27 9月, 2012 1 次提交