From: "Hemanth V" <hemanthv@ti.com>
To: Aaro Koskinen <aaro.koskinen@nokia.com>,
dbrownell@users.sourceforge.net,
spi-devel-general@lists.sourceforge.net
Cc: linux-omap@vger.kernel.org, Eero Nurkkala <ext-eero.nurkkala@nokia.com>
Subject: Re: [PATCH] OMAP: McSPI: Fix RX DMA transfer path
Date: Mon, 15 Jun 2009 10:58:47 +0530 [thread overview]
Message-ID: <005a01c9ed7a$2a5227b0$LocalHost@wipultra793> (raw)
In-Reply-To: 1244809910-4014-1-git-send-email-aaro.koskinen@nokia.com
----- Original Message -----
From: "Aaro Koskinen" <aaro.koskinen@nokia.com>
Subject: [PATCH] OMAP: McSPI: Fix RX DMA transfer path
> From: Eero Nurkkala <ext-eero.nurkkala@nokia.com>
>
> 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
WARNING: multiple messages have this Message-ID (diff)
From: "Hemanth V" <hemanthv@ti.com>
To: "Aaro Koskinen" <aaro.koskinen@nokia.com>,
<dbrownell@users.sourceforge.net>,
<spi-devel-general@lists.sourceforge.net>
Cc: <linux-omap@vger.kernel.org>,
"Eero Nurkkala" <ext-eero.nurkkala@nokia.com>
Subject: Re: [PATCH] OMAP: McSPI: Fix RX DMA transfer path
Date: Mon, 15 Jun 2009 10:58:47 +0530 [thread overview]
Message-ID: <005a01c9ed7a$2a5227b0$LocalHost@wipultra793> (raw)
In-Reply-To: 1244809910-4014-1-git-send-email-aaro.koskinen@nokia.com
----- Original Message -----
From: "Aaro Koskinen" <aaro.koskinen@nokia.com>
Subject: [PATCH] OMAP: McSPI: Fix RX DMA transfer path
> From: Eero Nurkkala <ext-eero.nurkkala@nokia.com>
>
> 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
next prev parent reply other threads:[~2009-06-15 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 12:31 [PATCH] OMAP: McSPI: Fix RX DMA transfer path Aaro Koskinen
[not found] ` <1244809910-4014-1-git-send-email-aaro.koskinen-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2009-06-13 16:37 ` Kalle Valo
2009-06-15 7:33 ` Tony Lindgren
2009-06-18 12:26 ` Kalle Valo
2009-06-15 5:28 ` Hemanth V [this message]
2009-06-15 5:28 ` Hemanth V
2009-06-15 8:37 ` Aaro Koskinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005a01c9ed7a$2a5227b0$LocalHost@wipultra793' \
--to=hemanthv@ti.com \
--cc=aaro.koskinen@nokia.com \
--cc=dbrownell@users.sourceforge.net \
--cc=ext-eero.nurkkala@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.