Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753109AbdF0MyX (ORCPT ); Tue, 27 Jun 2017 08:54:23 -0400 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:47338 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753372AbdF0MyP (ORCPT ); Tue, 27 Jun 2017 08:54:15 -0400 Date: Tue, 27 Jun 2017 22:54:14 +1000 (AEST) From: Finn Thain To: Michael Schmitz cc: Ondrej Zary , "James E.J. Bottomley" , "Martin K. Petersen" , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 0/4] g_NCR5380: PDMA fixes and cleanup In-Reply-To: <416a16e1-bbf0-87e0-3960-27a9a867e781@gmail.com> Message-ID: References: <201706262127.03911.linux@rainbow-software.org> <201706270828.40336.linux@rainbow-software.org> <416a16e1-bbf0-87e0-3960-27a9a867e781@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 442 Lines: 21 On Tue, 27 Jun 2017, Michael Schmitz wrote: > Ondrej, > > could this be a partial write (target did not transfer the last byte)? > We do wait for TCR_LAST_BYTE_SENT, but only when there is no residual. Perhaps we should wait for TCR_LAST_BYTE_SENT whenever the 53c400 asserts /EOP. That is, whenever BASR_END_DMA_TRANSFER is set. -- > One would suppose the chip posts a phase mismatch in that case ... > > Cheers, > > Michael >