Received: by 2002:a25:5b86:0:0:0:0:0 with SMTP id p128csp358469ybb; Thu, 28 Mar 2019 04:07:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqzNsul2llBNiMHh6RwtMJlKKB2MYJbHGv0PZWuSj7ZqEWGS/ibRZaCDApky9crylXYabLEl X-Received: by 2002:a17:902:bd41:: with SMTP id b1mr23308298plx.221.1553771220098; Thu, 28 Mar 2019 04:07:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553771220; cv=none; d=google.com; s=arc-20160816; b=ezu1tVMMBcfzf3A8fq+kncQJ0lNirND3YOb2plAGAhsyyTpUm+k+7OwH4lm/t0Rm/3 RL8JEA88ecfNA6ug5yR3rNLfvXNfNS3qrvXIZ/k0BcaWJOck/7zUcFXhnznmVtR3kouy /pZxrGXY0RaaZT6cg2Oh9C4gwKMP9owZwgYDJKDTRri2g+gAtVjBPdfQgEHwC5Zb2kG0 qnX/VMBva+ztMxkXm/nDDh3ukHeJVfY2wjrpyr2DwMoAq1sUX9e68aIY1/x6WNJUsWMC lQ1SiZrKJ51ebvLVlSUHtjgTUu77aIHCyWN633E0G4Wx7ViYvvJiAIfkxXORtgph6Ywt getw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=9zbeI7l5bnpaoj/Q6TqFXOcWMvxU6MDYlXf5emuANOc=; b=MXvGCED6z1p+Vy8K/fV30bVxaRdRoXZ4zIoOdELH7W5uTAliDdE4T0mdeJPjNSRLpQ Zveg1u9j5VlHO3pliIENJCzjoP2pr0vQfX/4I82+69hsHsCAYlAqy1wnQw0UNa+GwFmy EXr0eIu+tMqllGNPzFqkodF53HqAYVTqR/UNN5OdFf2395dLAD/EnvVRW3ogqSWsxMU0 kehW9gYWPE3I/A6nBhhdaiej4ekU4Die0YRYE7Pn7GRbYFifrO7cy6MYuImzHQovAeOI Cgs2qqP0lrAuCo8yu766WvVZbTYGkelo/u0756j4dC7sUdjsyj3fGvk1Mm6PLQsDixtv dLIA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=J0UUG+ma; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z9si9822994pln.65.2019.03.28.04.06.43; Thu, 28 Mar 2019 04:07:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=J0UUG+ma; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726221AbfC1LGG (ORCPT + 99 others); Thu, 28 Mar 2019 07:06:06 -0400 Received: from mail-lj1-f194.google.com ([209.85.208.194]:36066 "EHLO mail-lj1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725779AbfC1LGF (ORCPT ); Thu, 28 Mar 2019 07:06:05 -0400 Received: by mail-lj1-f194.google.com with SMTP id r24so16167551ljg.3; Thu, 28 Mar 2019 04:06:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=9zbeI7l5bnpaoj/Q6TqFXOcWMvxU6MDYlXf5emuANOc=; b=J0UUG+maTZnFJ3zLc6sdG6S50V3AsU2AyEJdaX4udTSrAW7yFWN2KTjrk4QMT0PSps XJLpAY2eA6JXbejkEklAUat0nqza4iDoKdMhQxfBaXzOZe4jkE7iyECHWBV33sVNw6pG t3JZZYwBJCqyXp8lJQOjOvOQFSdcDFTPHhleV8U18MxDzk0So20qRT7rvcTmrrkevhhT MOV7B+x/Jdm8RtD/UHhz9sM4NwcuYpmWIvftkuZ07LNA/SzGCfTlBnypk/3NJYBKn8gS LPDAVp22CLd7yeMnKsEpMB0jxgCtnUqFrwblLRfC+dSN1gcaL1Y3iKN4uU2LwHfQBcXg Bi9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=9zbeI7l5bnpaoj/Q6TqFXOcWMvxU6MDYlXf5emuANOc=; b=IniM9GkcXsc/2EUkjzaSMJ7mm06cVXoFG8kPMCPRYBdwUBgitE6VM4UM9BbGhIw//E r7NosOT98u6FvGNwaGiZXcMcd5pshzqiJJ7jsqFBuosID5QGpz9eKVjLjnIYJsRpMKb6 GsGw1tV4PRpm0X8om+nxu1wwD7WGNj+rhz5ycLdAdsCWNlvTvSHXMweM9bb26eomlVIU jtdsKyLSHmnik9q+eUJoaj31CWRGO1oaBVpLdHvK96vckVAqcGh/ov3KgFOl3ZeRUDya V0vMZTYg4sqve954UCLksCP0/MsgY3Y0clmdMRNwtmducAwLGbMq0UMki+zvKaVR2eFY AMlA== X-Gm-Message-State: APjAAAW8ijatRCFQSdl8q61LKukyYcYhf/rb4YfCpso8Dii/VB5grorf oGBohtprjReChl5zgWEXLDs= X-Received: by 2002:a2e:219:: with SMTP id 25mr19141796ljc.34.1553771162223; Thu, 28 Mar 2019 04:06:02 -0700 (PDT) Received: from [192.168.1.10] ([95.174.107.249]) by smtp.gmail.com with ESMTPSA id f18sm5064780lja.91.2019.03.28.04.06.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Mar 2019 04:06:01 -0700 (PDT) Subject: Re: Issues with i.MX SPI DMA transfers To: Robin Gong , =?UTF-8?Q?Uwe_Kleine-K=c3=b6nig?= Cc: "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-spi@vger.kernel.org" , dl-linux-imx , Fabio Estevam , Pengutronix Kernel Team , Sascha Hauer , Shawn Guo , Mark Brown , "dmaengine@vger.kernel.org" , Vinod Koul , Dan Williams , Andy Duan , Han Xu , Clark Wang References: <08fcbd65-510f-84f8-d6d6-ff56aa9ca9ad@gmail.com> <20190328065247.uz73lap7ljf5q3tb@pengutronix.de> From: Igor Plyatov Message-ID: Date: Thu, 28 Mar 2019 14:05:59 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Robin, I have applied patches 0001-dma-engine-imx-sdma-add-mcu_2_ecspi-script.patch, 0002-spi-spi-imx-fix-ERR009165.patch and made testing. Results are following: root@cr7:~# spidev_test -D /dev/spidev0.0 -s 12000000 -b 8 -S 512 -I 10000000000 -l spi mode: 0x20 bits per word: 8 max speed: 12000000 Hz (12000 KHz) [  133.987798] spi_imx 2008000.spi: I/O Error in DMA TX [  133.992810] spidev spi0.0: SPI transfer failed: -110 [  133.997860] spi_master spi0: failed to transfer one message from queue can't send spi message: Connection timed out Aborted (core dumped) root@cr7:~# spidev_test -D /dev/spidev1.0 -s 12000000 -b 8 -S 512 -I 10000000000 -l spi mode: 0x20 bits per word: 8 max speed: 12000000 Hz (12000 KHz) [  483.530815] spi_imx 200c000.spi: I/O Error in DMA TX [  483.535825] spidev spi1.0: SPI transfer failed: -110 [  483.540873] spi_master spi1: failed to transfer one message from queue can't send spi message: Connection timed out Aborted (core dumped) root@cr7:~# spidev_test -D /dev/spidev4.0 -s 12000000 -b 8 -S 512 -I 10000000000 -l spi mode: 0x20 bits per word: 8 max speed: 12000000 Hz (12000 KHz) [   94.228774] spi_imx 2018000.spi: I/O Error in DMA TX [   94.233788] spidev spi4.0: SPI transfer failed: -110 [   94.238837] spi_master spi4: failed to transfer one message from queue can't send spi message: Connection timed out Aborted (core dumped) Best wishes. -- Igor Plyatov > Hi Igor, > Please have a try with the attached patch, assume you have already used the sdma firmware > From https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/imx/sdma/sdma-imx6q.bin >> -----Original Message----- >> From: Igor Plyatov >> Sent: 2019年3月28日 15:04 >> To: Uwe Kleine-König >> Cc: linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; >> linux-spi@vger.kernel.org; dl-linux-imx ; Fabio Estevam >> ; Pengutronix Kernel Team ; >> Sascha Hauer ; Shawn Guo >> ; Mark Brown ; >> dmaengine@vger.kernel.org; Vinod Koul ; Dan Williams >> ; Andy Duan ; Han Xu >> ; Robin Gong ; Clark Wang >> >> Subject: Re: Issues with i.MX SPI DMA transfers >> >> Dear Uwe, >> >> >>> Hello Igor, >>> >>> On Wed, Mar 27, 2019 at 08:40:00PM +0300, Igor Plyatov wrote: >>>> please, help to resolve two issues with SPI DMA transfers at i.MX6Q >>>> platform. >>>> >>>> First issue is >>>>  [ 4465.008003] spi_master spi0: I/O Error in DMA RX >>>> >>>> Second issue is duplication for one of received bytes. >>>> >>>> Probably, these issues related to each one. >>> This is probably the same problem I hit some time ago. Check ERR009165 >>> in the errata. You either need to disable DMA or need a fixed >>> sdma-Script. >> disabling of DMA is not an option, because high throughput required for SPI bus >> to communicate with DSPs. >> >> I'm aware of ERR009165, but as I write some minutes earlier to list, >> spi0 (alias for ecspi1) and spi1 (alias for ecspi2) work flawless, while >> spi4 (alias for ecspi5) fails very fast. >> >> Does same SDMA script used for all SPI interfaces or scripts are different? >> >> Best wishes. >> >> -- >> >> Igor Plyatov