linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 2/6] dmaengine: mv_xor: add suspend/resume support
Date: Wed, 19 Aug 2015 22:23:49 +0530	[thread overview]
Message-ID: <20150819165349.GJ13546@localhost> (raw)
In-Reply-To: <20150729113405.2b337ae0@free-electrons.com>

On Wed, Jul 29, 2015 at 11:34:05AM +0200, Thomas Petazzoni wrote:
> Vinod,
> 
> On Wed, 22 Jul 2015 10:40:11 +0530, Vinod Koul wrote:
> 
> > > +static int mv_xor_suspend(struct platform_device *pdev, pm_message_t state)
> > > +{
> > > +	struct mv_xor_device *xordev = platform_get_drvdata(pdev);
> > > +	int i;
> > > +
> > > +	for (i = 0; i < MV_XOR_MAX_CHANNELS; i++) {
> > > +		struct mv_xor_chan *mv_chan = xordev->channels[i];
> > > +
> > > +		if (!mv_chan)
> > > +			continue;
> > > +
> > > +		mv_chan->saved_config_reg =
> > > +			readl_relaxed(XOR_CONFIG(mv_chan));
> > > +		mv_chan->saved_int_mask_reg =
> > > +			readl_relaxed(XOR_INTR_MASK(mv_chan));
> > this sound fine, but I am missing the suspension of the channel. If a
> > transfer was active while suspend was invoked then how would this work?
> 
> There are indeed no provisions to handle this problem. Does the
> dmaengine framework provide any helpers to ease with this? I have
> quickly looked at other dmaengine drivers, and I haven't seen any of
> them taking care of this problem. Do you have a pointer to a driver
> handling this problem?

Sorry for delay...

Should this be solved at framework level? We should rather suspend the
channels, save the cfg and then restore that on resume.

-- 
~Vinod

  reply	other threads:[~2015-08-19 16:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 14:28 [PATCHv4 0/6] dmaengine: mv_xor fixes and improvements Thomas Petazzoni
2015-07-08 14:28 ` [PATCHv4 1/6] dmaengine: mv_xor: fix big endian operation in register mode Thomas Petazzoni
2015-07-22  5:22   ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 2/6] dmaengine: mv_xor: add suspend/resume support Thomas Petazzoni
2015-07-22  5:10   ` Vinod Koul
2015-07-29  9:34     ` Thomas Petazzoni
2015-08-19 16:53       ` Vinod Koul [this message]
2015-07-08 14:28 ` [PATCHv4 3/6] dmaengine: mv_xor: remove support for dmacap, * DT properties Thomas Petazzoni
2015-07-22  5:16   ` [PATCHv4 3/6] dmaengine: mv_xor: remove support for dmacap,* " Vinod Koul
2015-07-22  5:18     ` Vinod Koul
2015-07-27 10:44     ` Thomas Petazzoni
2015-08-19 17:00       ` Vinod Koul
2015-08-19 17:02   ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 4/6] dmaengine: mv_xor: remove mv_xor_chan->current_type field Thomas Petazzoni
2015-08-19 17:04   ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 5/6] dmaengine: mv_xor: de-duplicate mv_chan_set_mode*() Thomas Petazzoni
2015-08-19 17:05   ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 6/6] dmaengine: mv_xor: optimize performance by using a subset of the XOR channels Thomas Petazzoni
2015-08-19 17:05   ` Vinod Koul
2015-07-08 15:37 ` [PATCHv4 0/6] dmaengine: mv_xor fixes and improvements Andrew Lunn

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=20150819165349.GJ13546@localhost \
    --to=vinod.koul@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).