1. 21 11月, 2019 14 次提交
  2. 05 9月, 2019 6 次提交
  3. 12 8月, 2019 3 次提交
  4. 29 7月, 2019 1 次提交
  5. 01 7月, 2019 3 次提交
  6. 27 6月, 2019 1 次提交
  7. 08 7月, 2019 1 次提交
  8. 16 6月, 2019 1 次提交
  9. 29 5月, 2019 4 次提交
    • O
      habanalabs: remove DMA mask hack for Goya · 2a51558c
      Oded Gabbay 提交于
      This patch removes the non-standard DMA mask setting for Goya. Now that
      the device CPU goes through the MMU, we are not limited to allocating the
      CPU accessible memory area in the address space of under 39 bits.
      Therefore, we don't need to set the DMA masking twice during
      initialization, a practice that is not working on POWER architecture.
      
      The patch sets the DMA mask to 48 bits once during the initialization. The
      address of the CPU accessible memory area is configured to the MMU and the
      matching VA is given to the device CPU.
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      2a51558c
    • O
      habanalabs: set Goya CPU to use ASIC MMU · f09415f5
      Oded Gabbay 提交于
      This patch configures the Goya CPU to actually go through the MMU for
      translation. The configuration is done after the configuration of the
      relevant MMU mappings.
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      f09415f5
    • O
      habanalabs: add MMU mappings for Goya CPU · 95b5a8b8
      Oded Gabbay 提交于
      This patch adds the necessary MMU mappings for the Goya CPU to access the
      device DRAM and the host memory.
      
      The first 256MB of the device DRAM is being mapped. That's where the F/W
      is running.
      
      The 2MB area located on the host memory for the purpose of communication
      between the driver and the device CPU is also being mapped.
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      95b5a8b8
    • O
      habanalabs: initialize device CPU queues after MMU init · 0b28d26b
      Oded Gabbay 提交于
      This patch changes the order of H/W IP initializations. The MMU needs to
      be initialized before the device CPU queues, because the CPU will go
      through the ASIC MMU in order to reach the host memory (where the queues
      are located).
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      0b28d26b
  10. 30 5月, 2019 2 次提交
  11. 25 5月, 2019 1 次提交
    • O
      habanalabs: halt debug engines on user process close · 89225ce4
      Omer Shpigelman 提交于
      This patch fix a potential bug where a user's process has closed
      unexpectedly without disabling the debug engines. In that case, the debug
      engines might continue running but because the user's MMU mappings are
      going away, we will get page fault errors.
      
      This behavior is also opposed to the general rule where nothing runs on
      the device after the user process closes.
      
      The patch stops the debug H/W engines upon process termination and thus
      makes sure nothing runs on the device after the process goes away.
      Signed-off-by: NOmer Shpigelman <oshpigelman@habana.ai>
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      89225ce4
  12. 17 5月, 2019 1 次提交
    • O
      habanalabs: don't limit packet size for device CPU · cbb10f1e
      Oded Gabbay 提交于
      This patch removes a limitation on the maximum packet size that is read by
      the device CPU as that limitation is not needed.
      
      Therefore, the patch also removes an elaborate calculation that is based
      on this limitation which is also not needed now. Instead, use a fixed
      value for the memory pool size of the packets.
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      cbb10f1e
  13. 16 5月, 2019 1 次提交
  14. 14 5月, 2019 1 次提交