All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@st.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Armando VISCONTI <armando.visconti@st.com>,
	Shiraz HASHIM <shiraz.hashim@st.com>,
	Vipin KUMAR <vipin.kumar@st.com>,
	Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
	Deepak SIKRI <deepak.sikri@st.com>,
	Vipul Kumar SAMAR <vipulkumar.samar@st.com>,
	Amit VIRDI <Amit.VIRDI@st.com>,
	Pratyush ANAND <pratyush.anand@st.com>,
	Bhupesh SHARMA <bhupesh.sharma@st.com>,
	"viresh.linux@gmail.com" <viresh.linux@gmail.com>,
	Bhavna YADAV <bhavna.yadav@st.com>,
	Vincenzo FRASCINO <Vincenzo.FRASCINO@st.com>,
	Mirko GARDI <mirko.gardi@st.com>
Subject: Re: [PATCH] dmaengine/dw_dmac: Reconfigure interrupt and chan_cfg register on resume
Date: Tue, 22 Nov 2011 11:50:15 +0530	[thread overview]
Message-ID: <4ECB3F1F.9060806@st.com> (raw)
In-Reply-To: <1321935206.1516.217.camel@vkoul-udesk3>

On 11/22/2011 9:43 AM, Vinod Koul wrote:
> On Thu, 2011-11-17 at 16:01 +0530, Viresh Kumar wrote:
>> > In S2R all DMA registers are reset by hardware and thus they are required to be
> When are they reset, whenever you leave channel idle or once you come
> back from suspend?

Whenever we do S2R, many power islands are switched off and so DMAC controller looses
all its power. On resume, all registers are in their reset state.

-- 
viresh

  reply	other threads:[~2011-11-22  6:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 10:31 [PATCH] dmaengine/dw_dmac: Reconfigure interrupt and chan_cfg register on resume Viresh Kumar
2011-11-22  4:13 ` Vinod Koul
2011-11-22  6:20   ` Viresh Kumar [this message]
2011-11-23 10:49     ` Vinod Koul
2011-11-23 11:11       ` Viresh Kumar
2011-11-23 11:32         ` Vinod Koul
2011-11-23 11:40           ` Viresh Kumar
2011-11-28  3:20 ` Vinod Koul

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=4ECB3F1F.9060806@st.com \
    --to=viresh.kumar@st.com \
    --cc=Amit.VIRDI@st.com \
    --cc=Vincenzo.FRASCINO@st.com \
    --cc=armando.visconti@st.com \
    --cc=bhavna.yadav@st.com \
    --cc=bhupesh.sharma@st.com \
    --cc=deepak.sikri@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mirko.gardi@st.com \
    --cc=pratyush.anand@st.com \
    --cc=rajeev-dlh.kumar@st.com \
    --cc=shiraz.hashim@st.com \
    --cc=vinod.koul@intel.com \
    --cc=vipin.kumar@st.com \
    --cc=vipulkumar.samar@st.com \
    --cc=viresh.linux@gmail.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 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.