From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hemanth V" Subject: Re: [PATCH] OMAP: McSPI: Fix RX DMA transfer path Date: Mon, 15 Jun 2009 10:58:47 +0530 Message-ID: <005a01c9ed7a$2a5227b0$LocalHost@wipultra793> References: <> <1244809910-4014-1-git-send-email-aaro.koskinen@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Return-path: Received: from bear.ext.ti.com ([192.94.94.41]:47740 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750891AbZFOF3A (ORCPT ); Mon, 15 Jun 2009 01:29:00 -0400 Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Aaro Koskinen , dbrownell@users.sourceforge.net, spi-devel-general@lists.sourceforge.net Cc: linux-omap@vger.kernel.org, Eero Nurkkala ----- Original Message ----- From: "Aaro Koskinen" Subject: [PATCH] OMAP: McSPI: Fix RX DMA transfer path > From: Eero Nurkkala > > When data is read through DMA, the last element must be read separately > through the RX register. It cannot be transferred by the DMA. For further > details see e.g. OMAP3430 TRM. Could you provide the section number and the version of TRM you are referring to. > > Without the fix the driver causes extra clocks to be clocked to the > bus after DMA RX operations. This can cause interesting behaviour with > some devices. Could you provide more details on the errors seen i.e is the transfer aborted Thanks Hemanth