From patchwork Wed Jan 24 12:43:15 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Siddharth Vadapalli X-Patchwork-Id: 13529186 Received: from fllv0015.ext.ti.com (fllv0015.ext.ti.com [198.47.19.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 74CE117543; Wed, 24 Jan 2024 12:43:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.19.141 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706100213; cv=none; b=k+FwdUibWSHn9jIx/sQCMFlRYgNF1Jd1AWBJgDFZbCLoTbxan/7bNP/AIXnQ8H8pmGtAKNOSI/Ocv9a1taoxZD+b9yaMum0bobeWKr6HRe/TaLm2WC00Y1l6NMBhL5k2JVt1O2a0dzkZPbFhhHYMsQ1Kf75GSN5fNNgzz6wBJ1M= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706100213; c=relaxed/simple; bh=zwa7JMLje9nKitQhpGBH/Ud+UJAbu+oPeCYwNYHUSz4=; h=From:To:CC:Subject:Date:Message-ID:MIME-Version:Content-Type; b=sE5JdaNRMjRNlgCj7GSjUDhdxt1CbYBQmXrmQt9T8LWOTD7Rc9IT8PzvFDGVonznDCrSk21CqZJ/rW7R3pwImDhNzM9zh+HVlmA9PtFg59bUbtZ/MCtVIj2UDOKFmY+wwirh85D5aQ5r7tRiwgZZFO+jk25Sblt2oZR/XI+s588= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com; spf=pass smtp.mailfrom=ti.com; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b=lunu1r62; arc=none smtp.client-ip=198.47.19.141 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="lunu1r62" Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 40OChNI7122886; Wed, 24 Jan 2024 06:43:23 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1706100203; bh=gVfyNk8drUt9KFdTpXp7vWMlSAAnrgR4hhKmmg7WHOA=; h=From:To:CC:Subject:Date; b=lunu1r62ZOWmxZ73z7J0gZxV6kghE7qOTIQWcst9/csBy/6d7ESln4F2XlmxbpOjG xpsLh8sz4PFN4P3fNhHLtm7Y1WZM0xC2QTRGtPatz2ocH5QkBqc3zwEjIx5vhHDMzt No5ZPblCSpMiXIxH3/TSX7uzVvIopfiZwFhskjR8= Received: from DLEE108.ent.ti.com (dlee108.ent.ti.com [157.170.170.38]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 40OChNdQ016265 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 24 Jan 2024 06:43:23 -0600 Received: from DLEE103.ent.ti.com (157.170.170.33) by DLEE108.ent.ti.com (157.170.170.38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 24 Jan 2024 06:43:22 -0600 Received: from lelvsmtp5.itg.ti.com (10.180.75.250) by DLEE103.ent.ti.com (157.170.170.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 24 Jan 2024 06:43:22 -0600 Received: from uda0492258.dhcp.ti.com (uda0492258.dhcp.ti.com [172.24.227.9]) by lelvsmtp5.itg.ti.com (8.15.2/8.15.2) with ESMTP id 40OChJPd014062; Wed, 24 Jan 2024 06:43:20 -0600 From: Siddharth Vadapalli To: , CC: , , , , , Subject: [PATCH v4 0/4] Add APIs to request TX/RX DMA channels for thread ID Date: Wed, 24 Jan 2024 18:13:15 +0530 Message-ID: <20240124124319.820002-1-s-vadapalli@ti.com> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: dmaengine@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 The existing APIs for requesting TX and RX DMA channels rely on parsing a device-tree node to obtain the Channel/Thread IDs from their names. However, it is possible to know the thread IDs by alternative means such as being informed by Firmware on a remote core via RPMsg regarding the allocated TX/RX DMA channel thread IDs. In such cases, the driver can be probed by non device-tree methods such as RPMsg-bus, due to which it is not necessary that the device using the DMA has a device-tree node corresponding to it. Thus, add APIs to enable the driver to make use of the existing DMA APIs even when there's no device-tree node. Additionally, since the name of the device for the remote RX channel is being set purely on the basis of the RX channel ID itself, it can result in duplicate names when multiple flows are used on the same channel. Avoid name duplication by including the flow in the name. Series is based on linux-next tagged next-20240124. v3: https://lore.kernel.org/r/20231218062640.2338453-1-s-vadapalli@ti.com/ Changes since v3: - Rebased series on linux-next tagged next-20240124. - Collected Acked-by tag from Peter Ujfalusi at: https://lore.kernel.org/r/4b5bd2c2-37c9-4cdf-934d-8bc6d6f73152@gmail.com/ for the series. v2: https://lore.kernel.org/r/20231212111011.1401641-1-s-vadapalli@ti.com/ Changes since v2: - Rebased series on linux-next tagged next-20231215. - Renamed the function "k3_udma_glue_request_tx_chn_by_id()" to "k3_udma_glue_request_tx_chn_for_thread_id()" as suggested by: Péter Ujfalusi - Similar to the above change, I have also renamed the function "k3_udma_glue_request_remote_rx_chn_by_id()" to "k3_udma_glue_request_remote_rx_chn_for_thread_id()". - Updated the function prototypes in include/linux/dma/k3-udma-glue.h accordingly. - Updated the commit messages for patches 3/4 and 4/4 to match the changes made to the function names. v1: https://lore.kernel.org/r/20231114083906.3143548-1-s-vadapalli@ti.com/ Changes since v1: - Rebased series on linux-next tagged next-20231212. - Updated commit messages with details regarding the use-case for which the newly added APIs will be required. - Removed unnecessary return value check within "of_k3_udma_glue_parse_chn()" function in patch 1, since it will fall through to "out_put_spec" anyway. - Removed unnecessary return value check within "of_k3_udma_glue_parse_chn_by_id()" function in patch 1, since it will fall through to "out_put_spec" anyway. - Moved patch 4 of v1 series to patch 2 of current series. RFC Series: https://lore.kernel.org/r/20231111121555.2656760-1-s-vadapalli@ti.com/ Changes since RFC Series: - Rebased patches 1, 2 and 3 on linux-next tagged next-20231114. - Added patch 4 to the series. Regards, Siddharth. Siddharth Vadapalli (4): dmaengine: ti: k3-udma-glue: Add function to parse channel by ID dmaengine: ti: k3-udma-glue: Update name for remote RX channel device dmaengine: ti: k3-udma-glue: Add function to request TX chan for thread ID dmaengine: ti: k3-udma-glue: Add function to request RX chan for thread ID drivers/dma/ti/k3-udma-glue.c | 306 ++++++++++++++++++++++--------- include/linux/dma/k3-udma-glue.h | 10 + 2 files changed, 229 insertions(+), 87 deletions(-)