Received: by 10.213.65.68 with SMTP id h4csp1022198imn; Sun, 25 Mar 2018 21:44:59 -0700 (PDT) X-Google-Smtp-Source: AG47ELu75Hfca04l2A6PjqNujLQrYyuOAyIs5CyrJ5uoCvWrLLL9O0PXf/2/RbUWoNQF1ddMmcID X-Received: by 2002:a17:902:2884:: with SMTP id f4-v6mr38600603plb.153.1522039499261; Sun, 25 Mar 2018 21:44:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522039499; cv=none; d=google.com; s=arc-20160816; b=0GxHkh4jnhn1T+cfcpsuWaieF4oec3xG1S5CzZT8M5nHxXdHCdWqNDvXLMdXJAPRcr jiqZmPaOFmUcCa+CWkj8rnsHQyXjPdZMpqaVh2vZqISsxipuYmLIZPhjBTWZT5QEf+Y9 npOyI8MaaEE060N4FRx0QZQVsk1zPijHpzdY1cyrRL56RxV3C0q2hm61V68S2/uaWHij DXgaXK36fXfG5uPkjaV8bfo6eeUI6ZuyZF9EMJJVdl1jWBCbK5GdDmV5p1o9FEbCQA/b RPOspUVORBnrGydLRScElAolOQ+JkplGlIEpQE7QOyIgT1L/l3PmL/zRgap5XZ6nIPu1 OXHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=Blnqs+T/MtPe4U8iCiCgX/zuG/Z3v+0uYeUhtEKsXb8=; b=eJsksp7IghYrhLcx8u1VNs03B7c+602iKUak4Lr8wMwZ9b1fUVYyMAVr9w9Co8H4L0 SsH0LEUZbUqpm3a/3h3w99aNB9ExfT8mK6HE3Lon0TCr0uOzQR/pbtLzXS/CWSZBIkwM KyJ8VXA9Y0FBJET0sLQvh/p0EGWFeqCZRi2FfG8cww6rNcmsBHCRQpzfAn0lSvnMPAvW PbwO9rUKO/dpnSrYyYtKceZO4TF7yvvCepUAycf3TZr3UpVWOxjyOmmVnqjS2p/Phb9Y sWbk92TX1U5fIUKW48DjlU5jFdMh53e7gkR9IkHdbZVXhD+bKTkJKC4yvidCPfOH+Nl7 J6eg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=k+rcyg5h; dkim=pass header.i=@codeaurora.org header.s=default header.b=k+rcyg5h; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z85si11166953pfk.194.2018.03.25.21.44.09; Sun, 25 Mar 2018 21:44:59 -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=@codeaurora.org header.s=default header.b=k+rcyg5h; dkim=pass header.i=@codeaurora.org header.s=default header.b=k+rcyg5h; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750928AbeCZElm (ORCPT + 99 others); Mon, 26 Mar 2018 00:41:42 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:60400 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750713AbeCZElk (ORCPT ); Mon, 26 Mar 2018 00:41:40 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id E57BE6071A; Mon, 26 Mar 2018 04:41:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1522039299; bh=3cMPyKCph/MbM6zcTOYoCqp0xaessuMKYz5O6dqVSYY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=k+rcyg5hegRwGbgfTwSnnN/ZBDsovZLlrpeagap87c2pZqdQHC4GP7UL2E+uFxt1A PjumbvwUKOHrQ9jdugeRK2aHkLK+PWVbCWKiVyXJIhckgQxSs/QTmzSaYM072XQ8gA yQ218eI/UqSKbtrZmysDQ5HlMB8AdJPb6I7WoM9U= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 514C3601EA; Mon, 26 Mar 2018 04:41:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1522039299; bh=3cMPyKCph/MbM6zcTOYoCqp0xaessuMKYz5O6dqVSYY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=k+rcyg5hegRwGbgfTwSnnN/ZBDsovZLlrpeagap87c2pZqdQHC4GP7UL2E+uFxt1A PjumbvwUKOHrQ9jdugeRK2aHkLK+PWVbCWKiVyXJIhckgQxSs/QTmzSaYM072XQ8gA yQ218eI/UqSKbtrZmysDQ5HlMB8AdJPb6I7WoM9U= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 26 Mar 2018 10:11:39 +0530 From: Abhishek Sahu To: Wolfram Sang Cc: Andy Gross , David Brown , Sricharan R , Austin Christ , linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 00/13] Major code reorganization to make all i2c transfers working In-Reply-To: <20180324122206.c4loxtob5o3lm7al@ninjato> References: <1520860502-14886-1-git-send-email-absahu@codeaurora.org> <20180324122206.c4loxtob5o3lm7al@ninjato> Message-ID: X-Sender: absahu@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-03-24 17:52, Wolfram Sang wrote: > On Mon, Mar 12, 2018 at 06:44:49PM +0530, Abhishek Sahu wrote: >> * v2: >> >> 1. Address review comments in v1 >> 2. Changed the license to SPDX >> 3. Changed commit messages for some of the patch having more detail >> 4. Removed event-based completion and changed transfer completion >> detection logic in interrupt handler >> 5. Removed dma_threshold and blk_mode_threshold from global structure >> 6. Improved determine mode logic for QUP v2 transfers >> 7. Fixed function comments >> 8. Fixed auto build test WARNING ‘idx' may be used uninitialized >> in this function >> 9. Renamed tx/rx_buf to tx/rx_cnt >> >> * v1: >> >> The current driver is failing in following test case >> 1. Handling of failure cases is not working in long run for BAM >> mode. It generates error message “bam-dma-engine 7884000.dma: >> Cannot >> free busy channel” sometimes. >> 2. Following I2C transfers are failing >> a. Single transfer with multiple read messages >> b. Single transfer with multiple read/write message with maximum >> allowed length per message (65K) in BAM mode >> c. Single transfer with write greater than 32 bytes in QUP v1 and >> write greater than 64 bytes in QUP v2 for non-DMA mode. >> 3. No handling is present for Block/FIFO interrupts. Any non-error >> interrupts are being treated as the transfer completion and then >> polling is being done for available/free bytes in FIFO. >> >> To fix all these issues, major code changes are required. This patch >> series fixes all the above issues and makes the driver interrupt based >> instead of polling based. After these changes, all the mentioned test >> cases are working properly. >> >> The code changes have been tested for QUP v1 (IPQ8064) and QUP >> v2 (IPQ8074) with sample application written over i2c-dev. >> >> Abhishek Sahu (13): >> i2c: qup: fix copyrights and update to SPDX identifier >> i2c: qup: fixed releasing dma without flush operation completion >> i2c: qup: minor code reorganization for use_dma >> i2c: qup: remove redundant variables for BAM SG count >> i2c: qup: schedule EOT and FLUSH tags at the end of transfer >> i2c: qup: fix the transfer length for BAM RX EOT FLUSH tags >> i2c: qup: proper error handling for i2c error in BAM mode >> i2c: qup: use the complete transfer length to choose DMA mode >> i2c: qup: change completion timeout according to transfer length >> i2c: qup: fix buffer overflow for multiple msg of maximum xfer len >> i2c: qup: send NACK for last read sub transfers >> i2c: qup: reorganization of driver code to remove polling for qup v1 >> i2c: qup: reorganization of driver code to remove polling for qup v2 > > Applied to for-next, thanks! Also thanks to the reviewers! Thanks Wolfram for your help in getting this big patch series applied to for-next. Thanks to Andy, Sricharan, Austin and other reviewers for reviewing/testing the patches. Regards, Abhishek