mbox series

[v4,0/3] Add compatible for Tegra234 GPCDMA

Message ID 20220720104045.16099-1-akhilrajeev@nvidia.com
Headers show
Series Add compatible for Tegra234 GPCDMA | expand

Message

Akhil R July 20, 2022, 10:40 a.m. UTC 
In cases where the client bus gets corrupted or if the end device
ceases to send/receive data, the DMA could wait for the data forever.
Tegra234 supports recovery of such channels hung in flush mode.

Add a separate compatible for Tegra234 so that this scenario can be
handled in the driver.

v3->v4:
    * Updated binding doc to use enum for compatible instead of const
v2->v3:
    * Updated binding docs and device tree compatible
v1->v2:
    * split device tree change to a different patch.
    * Update commit message


Akhil R (3):
  dt-bindings: dmaengine: Add compatible for Tegra234
  dmaengine: tegra: Add terminate() for Tegra234
  arm64: tegra: Update compatible for Tegra234 GPCDMA

 .../bindings/dma/nvidia,tegra186-gpc-dma.yaml |  4 ++-
 arch/arm64/boot/dts/nvidia/tegra234.dtsi      |  4 +--
 drivers/dma/tegra186-gpc-dma.c                | 26 +++++++++++++++++--
 3 files changed, 29 insertions(+), 5 deletions(-)

Comments

Vinod Koul July 26, 2022, 12:42 p.m. UTC | #1 
On 20-07-22, 16:10, Akhil R wrote:
> In cases where the client bus gets corrupted or if the end device
> ceases to send/receive data, the DMA could wait for the data forever.
> Tegra234 supports recovery of such channels hung in flush mode.
> 
> Add a separate compatible for Tegra234 so that this scenario can be
> handled in the driver.

Applied 1-2, thanks