From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (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 211D8277C81 for ; Wed, 25 Feb 2026 19:16:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772046992; cv=none; b=u+ok3Dxt/D6v34i36IQmJKBifdvQz1678fi21zTP88cTYVd0FKTUNUkv0w+c1NHBTfsKOPMd2g1iPawXxU/ANvXXKn6J7Y1S7tqm6dIoAk4O4hKLn/XKtoGd4ChX5CYaSYTyY4F22p5nVds65FzHTI6VtL6Z1kqoE3Jv0n4ms1I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772046992; c=relaxed/simple; bh=JKDW/3JaTVDQQN1HGh2Kx50563O3XSftBtp3y9MuSmc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=LEOGLiXusMlKTpqaHfXHD3ma44EXCaNVDRijtp9qAUiMl28xpwPEuFWsqdddW9p3j9xnzdM5DveUhe2T9apIGRbTGGhDkbEGah5JhcYlK3uIgdbmJptEUK6ejdok8HyL5kFurLXsMyff6OUHka+cu62g1zTTvJEuIkDrRf/pobs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=NBIuGH+q; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=judDxENA; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="NBIuGH+q"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="judDxENA" Received: from pps.filterd (m0279866.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 61PH3n3p1195992 for ; Wed, 25 Feb 2026 19:16:30 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= kdS/QntJSaGj5m5uHLTyiULnHKwPg/+0nR+soa0YEdU=; b=NBIuGH+qsITYkPXs Lof0N/6lSzDAv7Bpsm1A94Chi6YXXVYgoHooLmZ82JXaMITNohWCFCF5VA++xnoN yFJorSI5utmoSnY1IhQPWMnBVJp91XxB28WwAFzWVEGN3qSiQZCVtHkO5nZsRo2c JpJvOGSulZmLVv3Ty54oc1DNU2nIwPiaHIsLPqsoM1WW3qQCi34G+Bvjexxh6JlM uafSnrGYntn6CiqjATlu+MZVNOrBjrL6486X76+gARLA1z3DqX0pMoQtPXmQWMhN YH7S0MKzRKnXfjyz3xCY97lqnaDBIvi8uc5BjAJfkuSc/hfMmthY1ejzMJHJ1Gi+ Zxh29A== Received: from mail-dy1-f200.google.com (mail-dy1-f200.google.com [74.125.82.200]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4cj559ge2w-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Wed, 25 Feb 2026 19:16:30 +0000 (GMT) Received: by mail-dy1-f200.google.com with SMTP id 5a478bee46e88-2bdc0bb5ea0so867eec.1 for ; Wed, 25 Feb 2026 11:16:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1772046989; x=1772651789; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=kdS/QntJSaGj5m5uHLTyiULnHKwPg/+0nR+soa0YEdU=; b=judDxENASDtWRPk1RjrdYNQmPdZ6zl83fwVveVZG/dekj2O7E+UmeJxAc9KwrzCx1x UI53kcbj5D+4B0ZmOJL+9zZBnX2ZsobAF+q8LwXic8yJCDRIXeUvFDBctogM6jwNs2Zj tGh5FNh00YR0/xrs1yrFIQvplo2/3kQO3382RiNuT4O8gQwHaeaBc8KGnjGqWK8kO/u+ XKgw3Ghj97pFsZu1zBhqBD5D9kj5qr+KJZqGs2iXLhUkBBVhlawPb4cC6adQfPvkX5x3 cwuB5mOKK7aZOE4sCNiFHhHYaI9q/xJCmCP9zGXboccwuwtmkj3p1apDnL2H3Nir7GLP qF6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1772046989; x=1772651789; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=kdS/QntJSaGj5m5uHLTyiULnHKwPg/+0nR+soa0YEdU=; b=kxnfmBHfHNsVJT+ILdxVXKujDMDfgHsjGGjmIBHdTvUVCexBkMkzE8dHO2rRigHfri PGx0UMEbm1718kZLJf6KirO5hELVoW0fZN2M2CV+SLMYQncnk/PYPQg/wWDxX2FioNQO JTHj6ZYCOpUUERP0oayoMFV38ivEepXLKleNNAqlskaQTCIEKTvHA5GTVEk8nPDdniMV wgPP58SKlEj7b0veWRhGxu6vn8uQG57Q7IV7A8h1Y0M17p53u6UpfNPGbpe4upVjssLR MoYi/jHpph5Z78pi6eN6jUOcy78eGNLc79/WtxtBvI8p2t6WNy6KeW0/vC7hEwTviGVk vlHQ== X-Forwarded-Encrypted: i=1; AJvYcCVwUqRwh/BU4T3yBqR+JrNkB8GNHmkuOZ2H23K0js2hndXR8Mkkf+OhHYmpw5EtByuqUVPZDL47pE2IFJQ=@vger.kernel.org X-Gm-Message-State: AOJu0Yy04o/EkDfkKGQJCLz+rCD0FiDPWzSuj1tjEVz8rf6MktgnVO8a hnxK5hEXqlv3ptc1HQsW9C7k5XYhxP0UTK/MuhlA4Ntmw4X+Nh8cE0CBmeCYjPIKZ8MqJwDk/40 YZHbUrlyMzizFxXoRkWcB5wVC74LJhZRLBP5IIkvbZe8fCE9fKhZp+EPJFWeA/gzZo40= X-Gm-Gg: ATEYQzwhsdA9Wmh7ccTGR4uFHLFlrLNmp2wqyux28LQG1tA007LRUpk6vtlBjOAKXDW r2P1E4uFvRmg2pfhTUzVog/a/Enlm5pnqXQS/d/MugQl99mZnnhNg2pbaHrTURwbmp8APP97tDh 6i15tZOX3mdBBl3qGxgk11dmlrlYL4aT8UYtmtZEomZXfeE8c6OSTmj7oUOl6XN4d2sPbRVYR8u zwbq/aHje31TJ8ZK+pJmJXe2CwIU/Vk4BSE9NxRFXmHo+iEFZR+N3lSseGtR88jA4QkqEPucm2n Z+q8ZTb32Pz1G14+a1mxJLQoeMqkvdUQS//q3a+8+M8SYAQDVs6lMxXU4/lyJlSCc5TdKaWLaow 4JVtna8dN20GGqoLkFKHjUJHwnwVk7ZJClyqqKKODEgE69weKzMyKWFU= X-Received: by 2002:a05:7301:434b:b0:2ba:990a:4829 with SMTP id 5a478bee46e88-2bd7bd112fcmr7841927eec.30.1772046989283; Wed, 25 Feb 2026 11:16:29 -0800 (PST) X-Received: by 2002:a05:7301:434b:b0:2ba:990a:4829 with SMTP id 5a478bee46e88-2bd7bd112fcmr7841890eec.30.1772046988649; Wed, 25 Feb 2026 11:16:28 -0800 (PST) Received: from [192.168.86.165] ([76.176.48.107]) by smtp.gmail.com with ESMTPSA id 5a478bee46e88-2bd7dbe8304sm9699189eec.17.2026.02.25.11.16.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 25 Feb 2026 11:16:28 -0800 (PST) Message-ID: <4e4b50fe-1091-451e-b854-f7b061ebd88d@oss.qualcomm.com> Date: Wed, 25 Feb 2026 11:16:26 -0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH RFC 01/18] accel/qda: Add Qualcomm QDA DSP accelerator driver docs To: Bjorn Andersson , Ekansh Gupta Cc: Oded Gabbay , Jonathan Corbet , Shuah Khan , Joerg Roedel , Will Deacon , Robin Murphy , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Sumit Semwal , =?UTF-8?Q?Christian_K=C3=B6nig?= , dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, iommu@lists.linux.dev, linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org, Srinivas Kandagatla , Dmitry Baryshkov , Bharath Kumar , Chenna Kesava Raju References: <20260224-qda-firstpost-v1-0-fe46a9c1a046@oss.qualcomm.com> <20260224-qda-firstpost-v1-1-fe46a9c1a046@oss.qualcomm.com> <5a278b02-f2ad-408b-b0ad-f2297817bd7e@oss.qualcomm.com> Content-Language: en-US From: Trilok Soni In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Proofpoint-ORIG-GUID: e7OmJ5tvlyCLF8ybD48EFfj-cqMvyNvq X-Proofpoint-GUID: e7OmJ5tvlyCLF8ybD48EFfj-cqMvyNvq X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMjI1MDE4MCBTYWx0ZWRfXzlCk2ZnYL8P/ IhgeuvE6GEaPWvQSNazABdYlFCkI4YfQ1mXLF7x1FC8TOF8s/AMkueG7Ed8IPbyqX3DEIoAwa59 CYaE9No3z2OcoDfAh6wHlV5XKtX0qQdgBqCnoTSXSKkei3/Gz2Uej+XTlq09nC/4TZFD5xWg3ju a+1raTaQpEdOxPo+cQ+WjtQCgTqU/SCSvi8CAyumtoYzyZ0tOM29MprD10E+kmdIvCk47MCGw++ M8mEhOiVazDTh1OUeWSHT31B3W93dMX9RjPk2eeEFEvGvB+gPdeGuvONDfgXr6DQuo4HmlbM9SP klJQa8zPN77qeokDOI1xadhGeQ2kVS5Vixxj/emmGedOMeLwdgLzctk9E4548nR+FzX1nD8h2Im mE9L1o3tvx8B0OZOVqHaPq8D2mblL8+q92Fm2sQ4unqqvcbw4YWMrN0ugdnjIuHvvgf8YQpcH/+ lF3ogutLNGi3t8iIrDg== X-Authority-Analysis: v=2.4 cv=TcybdBQh c=1 sm=1 tr=0 ts=699f4a8e cx=c_pps a=PfFC4Oe2JQzmKTvty2cRDw==:117 a=lsoD3MMNObdLvy1227ExmA==:17 a=IkcTkHD0fZMA:10 a=HzLeVaNsDn8A:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=u7WPNUs3qKkmUXheDGA7:22 a=YMgV9FUhrdKAYTUUvYB2:22 a=Vs6AG_5Z_IHWLNxo5LUA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=6Ab_bkdmUrQuMsNx7PHu:22 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.51,FMLib:17.12.100.49 definitions=2026-02-25_02,2026-02-25_01,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 suspectscore=0 bulkscore=0 malwarescore=0 lowpriorityscore=0 clxscore=1015 spamscore=0 impostorscore=0 phishscore=0 priorityscore=1501 adultscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2602130000 definitions=main-2602250180 On 2/25/2026 7:12 AM, Bjorn Andersson wrote: > On Wed, Feb 25, 2026 at 07:47:08PM +0530, Ekansh Gupta wrote: >> >> >> On 2/24/2026 9:03 AM, Trilok Soni wrote: >>> On 2/23/2026 11:08 AM, Ekansh Gupta wrote: >>>> Add initial documentation for the Qualcomm DSP Accelerator (QDA) driver >>>> integrated in the DRM accel subsystem. >>>> >>>> The new docs introduce QDA as a DRM/accel-based implementation of >>>> Hexagon DSP offload that is intended as a modern alternative to the >>>> legacy FastRPC driver in drivers/misc. The text describes the driver >>>> motivation, high-level architecture and interaction with IOMMU context >>>> banks, GEM-based buffer management and the RPMsg transport. >>>> >>>> The user-space facing section documents the main QDA IOCTLs used to >>>> establish DSP sessions, manage GEM buffer objects and invoke remote >>>> procedures using the FastRPC protocol, along with a typical lifecycle >>>> example for applications. >>>> >>>> Finally, the driver is wired into the Compute Accelerators >>>> documentation index under Documentation/accel, and a brief debugging >>>> section shows how to enable dynamic debug for the QDA implementation. >>> So existing applications written over character device UAPI needs to be >>> rewritten over new UAPI and it will be broken once this driver gets >>> merged? Are we going to keep both the drivers in the Linux kernel >>> and not deprecate the /char device one? >>> >>> Is Qualcomm going to provide the wrapper library in the userspace >>> so that existing applications by our customers and developers >>> keep working w/ the newer kernel if the char interface based >>> driver gets deprecated? It is not clear from your text above. >> Thanks for raising this, Trilok. >> >> This is one of the open items that I have. I'm not exactly sure what would be the >> acceptable way for this.  >> >> As you mentioned, applications that rely on /dev/fastrpc* might not work on QDA >> without modification. >> >> I was thinking in the same lines as you have mentioned and  having some shim/compat >> driver to translate FastRPC UAPI to QDA. The compat driver would expose the existing >> character devices and route the calls to QDA. The compat driver could be built via Kconfig. >> > > This is a fundamental requirement, you need to address this in order for > this to move forward. > > Which makes me wonder if it would be possible to reach an accel driver > through incremental transition of the current driver, instead of just > dropping in a few thousand lines of new code/design. > >> However, I haven’t encountered an example of such a UAPI‑translation driver in the kernel >> before, so I would want guidance from maintainers on whether this is an acceptable >> model or not. >> >> Regarding your question about library, all the APIs exposed by github/fastrpc library are kept >> unchanged in terms of definitions and expectation. The same project can be build for both >> FastRPC and QDA based on configure options. So, the applications using github/fastrpc should >> not face any problem if the libs is built with proper configure options. >> > > You're assuming that the kernel and userspace are a unified piece of > software, they are not. It must be possible for me to install a new > kernel package without having to replace the userspace libraries. Thank you Bjorn for providing the inputs. I also foresee that we will be stop adding (or already happened) new features into the existing fastrpc driver, so calling the new driver as an alternative is in oversold category. You are pretty much began the deprecating the existing fastrpc driver, so let's just mention it if that is the case and provide migration/shim path so that existing binaries doesn't break. ---Trilok Soni