From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from www522.your-server.de (www522.your-server.de [195.201.215.122]) (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 23435472773; Thu, 26 Feb 2026 20:06:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=195.201.215.122 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772136394; cv=none; b=qBm8j0xrF/bDNqs0qMyXyZAcwNFH2YWLsmbhejDqT5aHVA5OgfWpiCzKukSNQ4SfSJnHyiJNCNK5dyFRAyOV2AEWKCdsyiD8p9C9ASNpCJv5myxfCbX5F6rUzhQNEHg11++hzBSzzBKIEwaSuq/brmWkwqREucUSqimtIkqzzkc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772136394; c=relaxed/simple; bh=rbEs8dxzXbyXsx8YK4dlXjrGx2Ow+1Um/bUSwRd3lJE=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:From:To: References:In-Reply-To; b=N2kTxbkAFlKN8M0QCkUYGrEvQ0eOMkYJn0gx4XidZ+UVWklsFWsEFAb9f36m8mE+GRQEzKxk7KjilNZ8vgyyTZ3XwtDo8KsPis259zOKuWj0z6JVOZSi5vSqTroOP71is4MMGr2Wpg9ON701+zWeSSM64v2FqAuZ9xzszru/gZQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=folker-schwesinger.de; spf=pass smtp.mailfrom=folker-schwesinger.de; dkim=pass (2048-bit key) header.d=folker-schwesinger.de header.i=@folker-schwesinger.de header.b=h9S+qVYj; arc=none smtp.client-ip=195.201.215.122 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=folker-schwesinger.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=folker-schwesinger.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=folker-schwesinger.de header.i=@folker-schwesinger.de header.b="h9S+qVYj" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=folker-schwesinger.de; s=default2212; h=In-Reply-To:References:To:From:Cc: Subject:Message-Id:Date:Content-Type:Content-Transfer-Encoding:Mime-Version: Sender:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=eCF8FWWOPs/3jZyvVWyjhhPvbHufnb1Suj0O602BVrM=; b=h9S+qVYjNEMQ6kGtSE0q8TcTUh BGyh8q1C4GjmMVF0102QFSNsuohfUtgqn5fgkgjC9ui/Q1fvua51GzqsFnm/ZAlQkgTr4tJlJhQeK kA9whG67+KnM0jGqdjiEB8Yp337rBz2YegWRzyG8YrRidZ1DGR7NQw1gXoMG+Xl5h/hc2/TMJyzvM wxwHkkdTx39ifFTymK744ARG3V/Ct/GEZzLB811u+tVQSFUDaZ4EkKL5pCjx9Ug/y2M8PbmBruCMC zZ8EYCt+6dMjgL8wWjDNoI9w1k4r4WBVHsTHqcqiBpPNlFoO42qlC2E5XiFW9HwLuBcn8/9sMtWfC DIwEYbUw==; Received: from sslproxy07.your-server.de ([78.47.199.104]) by www522.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from ) id 1vvhci-000PKH-1n; Thu, 26 Feb 2026 21:06:12 +0100 Received: from localhost ([127.0.0.1]) by sslproxy07.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vvhcg-0009t4-2f; Thu, 26 Feb 2026 21:06:11 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 26 Feb 2026 20:06:07 +0000 Message-Id: Subject: Re: [RFC PATCH] dmaengine: xilinx_dma: Fix per-channel direction reporting via device_caps Cc: "Rahul Navale" , , , , , , , , , , , , From: "Folker Schwesinger" To: "Rahul Navale" X-Mailer: aerc 0.21.0-119-g0a449d4a7ff3 References: <20260226073512.4595-1-rahulnavale04@gmail.com> In-Reply-To: <20260226073512.4595-1-rahulnavale04@gmail.com> X-Virus-Scanned: Clear (ClamAV 1.4.3/27924/Thu Feb 26 08:24:13 2026) Hi Rahul, On Thu Feb 26, 2026 at 8:35 AM CET, Rahul Navale wrote: > root@pdm3:~# aplay closetoyou.wav > Playing WAVE 'closetoyou.wav' : Signed 16 bit Little Endian, Rate 48000 H= z, Stereo > > aplay: pcm_write:2178: write error: Interrupted system call > root@pdm3:~# aplay closetoyou.wav root@pdm3:~# dmesg | grep xilinx_dma_de= vice_caps > [ 0.318827] xilinx_dma_device_caps: caps->directions =3D 0x00000001 > [ 0.318832] xilinx_dma_device_caps: caps->directions =3D 0x00000001 > [ 0.319170] xilinx_dma_device_caps: caps->directions =3D 0x00000002 > [ 0.319175] xilinx_dma_device_caps: caps->directions =3D 0x00000002 > [ 6.375745] xilinx_dma_device_caps: caps->directions =3D 0x00000001 > [ 6.375762] xilinx_dma_device_caps: caps->directions =3D 0x00000001 > [ 133.401497] xilinx_dma_device_caps: caps->directions =3D 0x00000001 > [ 133.401513] xilinx_dma_device_caps: caps->directions =3D 0x00000001 > [ 167.802636] xilinx_dma_device_caps: caps->directions =3D 0x00000001 > [ 167.802651] xilinx_dma_device_caps: caps->directions =3D 0x00000001 Looks like direction aggregation does not actually happen in your case. Probably because you have two distinct DMA devices with a single channel each. Could you confirm this from your DT? This suggests, that direction aggregation is not the actual root cause of the regression you're seeing. Maybe 7e01511443c3 exposes/triggers another subtle flaw in the ASoC or DMA layers or your driver. But that's speculation at this point. I'm not sure how to proceed from here. I think the patch itself is functional, but it does not address the actual issue. There's however one other thing you could test: Could you keep the RFC patch with the printks in place, but revert 7e01511443c3, rerun and post the logs?