1. 28 Jun, 2016 2 commits
    • Megha Dey's avatar
      crypto: sha512-mb - SHA512 multibuffer job manager and glue code · 8c603ff2
      Megha Dey authored
      This patch introduces the multi-buffer job manager which is responsible
      for submitting scatter-gather buffers from several SHA512 jobs to the
      multi-buffer algorithm. It also contains the flush routine that's called
      by the crypto daemon to complete the job when no new jobs arrive before
      the deadline of maximum latency of a SHA512 crypto job.
      
      The SHA512 multi-buffer crypto algorithm is defined and initialized in this
      patch.
      Signed-off-by: default avatarMegha Dey <megha.dey@linux.intel.com>
      Reviewed-by: default avatarFenghua Yu <fenghua.yu@intel.com>
      Reviewed-by: default avatarTim Chen <tim.c.chen@linux.intel.com>
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
      8c603ff2
    • Arnd Bergmann's avatar
      crypto: ux500 - do not build with -O0 · 9ac1c320
      Arnd Bergmann authored
      The ARM allmodconfig build currently warngs because of the
      ux500 crypto driver not working well with the jump label
      implementation that we started using for dynamic debug, which
      breaks building with 'gcc -O0':
      
      In file included from /git/arm-soc/include/linux/jump_label.h:105:0,
                       from /git/arm-soc/include/linux/dynamic_debug.h:5,
                       from /git/arm-soc/include/linux/printk.h:289,
                       from /git/arm-soc/include/linux/kernel.h:13,
                       from /git/arm-soc/include/linux/clk.h:16,
                       from /git/arm-soc/drivers/crypto/ux500/hash/hash_core.c:16:
      /git/arm-soc/arch/arm/include/asm/jump_label.h: In function 'hash_set_dma_transfer':
      /git/arm-soc/arch/arm/include/asm/jump_label.h:13:7: error: asm operand 0 probably doesn't match constraints [-Werror]
        asm_volatile_goto("1:\n\t"
      
      Turning off compiler optimizations has never really been supported
      here, and it's only used when debugging the driver. I have not found
      a good reason for doing this here, other than a misguided attempt
      to produce more readable assembly output. Also, the driver is only
      used in obsolete hardware that almost certainly nobody will spend
      time debugging any more.
      
      This just removes the -O0 flag from the compiler options.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
      9ac1c320
  2. 27 Jun, 2016 10 commits
  3. 24 Jun, 2016 8 commits
  4. 23 Jun, 2016 20 commits