From: Nishanth Menon <nm@ti.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: linux-omap@vger.kernel.org,
Kevin Hilman <khilman@deeprootsystems.com>,
Paul Walmsley <paul@pwsan.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4] OMAP2+: PM: omap device: API's for handling mstandby mode
Date: Fri, 19 Nov 2010 09:32:42 -0600 [thread overview]
Message-ID: <4CE6989A.7070007@ti.com> (raw)
In-Reply-To: <1290151312-347-1-git-send-email-manjugk@ti.com>
G, Manjunath Kondaiah had written, on 11/19/2010 01:21 AM, the following:
> Certain errata's in OMAP2+ processors will require forcing
> master standby to "no standby" mode before completing on going
> operation. Without this, the results will be unpredictable.
>
[..]
> These API's are required for multiple DMA errata's which require
> putting DMA controller in no mstandby mode before stopping dma.
>
> The applicable errata's:
> 1. Errata ID: i557(Applicable for omap36xx all ES versions)
> The channel hangs when the Pause bit (DMA4_CDPi [7] ) is cleared
> through config port while in Standby.
>
> 2. Errata ID: i541(all omap2plus except omap4)
> sDMA FIFO draining does not finish
>
> 3. OMAP3430 ES1.0(Errata ID:i88) will require DMA to be put in
> no mstandby mode before disabling the channel after completing
> the data transfer operation.
Minor feedback from what I got from an offline comment:
1 bug = Erratum
1+ bug = Errata
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2010-11-19 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 7:21 [PATCH v4] OMAP2+: PM: omap device: API's for handling mstandby mode G, Manjunath Kondaiah
2010-11-19 15:32 ` Nishanth Menon [this message]
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=4CE6989A.7070007@ti.com \
--to=nm@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=paul@pwsan.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).