1. 03 6月, 2015 1 次提交
    • D
      crypto: nx - prevent nx 842 load if no hw driver · 3e648cbe
      Dan Streetman 提交于
      Change the nx-842 common driver to wait for loading of both platform
      drivers, and fail loading if the platform driver pointer is not set.
      Add an independent platform driver pointer, that the platform drivers
      set if they find they are able to load (i.e. if they find their platform
      devicetree node(s)).
      
      The problem is currently, the main nx-842 driver will stay loaded even
      if there is no platform driver and thus no possible way it can do any
      compression or decompression.  This allows the crypto 842-nx driver
      to load even if it won't actually work.  For crypto compression users
      (e.g. zswap) that expect an available crypto compression driver to
      actually work, this is bad.  This patch fixes that, so the 842-nx crypto
      compression driver won't load if it doesn't have the driver and hardware
      available to perform the compression.
      Signed-off-by: NDan Streetman <ddstreet@ieee.org>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      3e648cbe
  2. 11 5月, 2015 4 次提交
  3. 25 11月, 2014 1 次提交
    • G
      of/reconfig: Always use the same structure for notifiers · f5242e5a
      Grant Likely 提交于
      The OF_RECONFIG notifier callback uses a different structure depending
      on whether it is a node change or a property change. This is silly, and
      not very safe. Rework the code to use the same data structure regardless
      of the type of notifier.
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
      Cc: <linuxppc-dev@lists.ozlabs.org>
      f5242e5a
  4. 24 7月, 2014 1 次提交
    • G
      of: Reorder device tree changes and notifiers · 259092a3
      Grant Likely 提交于
      Currently, devicetree reconfig notifiers get emitted before the change
      is applied to the tree, but that behaviour is problematic if the
      receiver wants the determine the new state of the tree. The current
      users don't care, but the changeset code to follow will be making
      multiple changes at once. Reorder notifiers to get emitted after the
      change has been applied to the tree so that callbacks see the new tree
      state.
      
      At the same time, fixup the existing callbacks to expect the new order.
      There are a few callbacks that compare the old and new values of a
      changed property. Put both property pointers into the of_prop_reconfig
      structure.
      
      The current notifiers also allow the notifier callback to fail and
      cancel the change to the tree, but that feature isn't actually used.
      It really isn't valid to ignore a tree modification provided by firmware
      anyway, so remove the ability to cancel a change to the tree.
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Cc: Nathan Fontenot <nfont@austin.ibm.com>
      259092a3
  5. 20 6月, 2014 1 次提交
  6. 29 5月, 2014 1 次提交
  7. 16 4月, 2014 1 次提交
  8. 11 2月, 2014 1 次提交
    • N
      crypto/nx/nx-842: Fix handling of vmalloc addresses · 0ba3e101
      Nathan Fontenot 提交于
      The powerpc specific nx-842 compression driver does not currently
      handle translating a vmalloc address to a physical address.
      
      The current driver uses __pa() for all addresses which does not
      properly handle vmalloc addresses and thus causes a failure since
      we do not pass a proper physical address to the hypervisor.
      
      This patch adds a routine to convert an address to a physical
      address by checking for vmalloc addresses and handling them properly.
      Signed-off-by: NNathan Fontenot <nfont@linux.vnet.ibm.com>
       ---
       drivers/crypto/nx/nx-842.c |   29 +++++++++++++++++++----------
       1 file changed, 19 insertions(+), 10 deletions(-)
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      0ba3e101
  9. 15 11月, 2012 1 次提交
  10. 20 8月, 2012 1 次提交
  11. 01 8月, 2012 1 次提交