linux-kernel - [PATCH v4 0/3] Add compatible for Tegra234 GPCDMA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220720104045.16099-1-akhilrajeev@nvidia.com>
Date:   Wed, 20 Jul 2022 16:10:42 +0530
From:   Akhil R <akhilrajeev@...dia.com>
To:     <dmaengine@...r.kernel.org>, <jonathanh@...dia.com>,
        <ldewangan@...dia.com>, <linux-kernel@...r.kernel.org>,
        <linux-tegra@...r.kernel.org>, <p.zabel@...gutronix.de>,
        <thierry.reding@...il.com>, <vkoul@...nel.org>,
        <robh+dt@...nel.org>, <devicetree@...r.kernel.org>
CC:     <akhilrajeev@...dia.com>
Subject: [PATCH v4 0/3] Add compatible for Tegra234 GPCDMA

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(-)

-- 
2.17.1