From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] dmaengine: at_xdmac: simplify channel configuration stuff
Date: Thu, 11 Dec 2014 10:12:20 +0530 [thread overview]
Message-ID: <20141211044220.GG16827@intel.com> (raw)
In-Reply-To: <20141209095030.GI27228@ldesroches-Latitude-E6320>
On Tue, Dec 09, 2014 at 10:50:30AM +0100, Ludovic Desroches wrote:
> > > > only thing here wer are saving and restoring from save_cc. How does that
> > > > impact rest of the code above?
> > this part is the only one which is clear. I think right way would be to
> > split these changes and explain in each one why we are doing them. Down
> > the line when someone is working on this will know precisely why this change
> > was made. Two years is a long time, even we will forget. So good changelog
> > and splitting patches to do just one thing is very helpful
>
> I don't see why this patch should be split. The goal is to remove the
> configuration register snapshot and to put it in the lli descriptor.
> Because I am removing this snapshot, I have to update suspend/resume and
> the way I have chosen is to directly get the value from the hardware
> register. If it is a blocking point I'll split it. I think you want me
> to put the addition of the save_cc field into another patches but I have
> no reason to do it before patch 2 since I have not encountered any bug
> yet (even if I think it is safer). And if I don't do it in patch 2,
> suspend/resume will be broken.
cant the save cc bits come first and then rest of contents in this patch
>
>
> About the commit message I could elaborate a bit more:
>
> This patch simplifies the channel configuration register management.
> Relying on a "software snapshot" of the configuration is not safe and
> too complex.
>
> Multiple dwidths will be introduced for slave transfers. In this case,
> it becomes quite difficult to have an accurate snapshot of the channel
> configuration register in the way it is done. Using the channel
> configuration available in the lli descriptor simplifies this stuff.
much better :)
--
~Vinod
next prev parent reply other threads:[~2014-12-11 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 16:22 [PATCH 0/3] dmaengine: at_xdmac: several improvements Ludovic Desroches
2014-11-26 16:22 ` [PATCH 1/3] dmaengine: at_xdmac: wait for in-progress transaction to complete after pausing a channel Ludovic Desroches
2014-11-26 16:22 ` [PATCH 2/3] dmaengine: at_xdmac: simplify channel configuration stuff Ludovic Desroches
2014-12-08 10:39 ` Vinod Koul
2014-12-08 14:05 ` Ludovic Desroches
2014-12-09 6:13 ` Vinod Koul
2014-12-09 9:50 ` Ludovic Desroches
2014-12-11 4:42 ` Vinod Koul [this message]
2014-11-26 16:22 ` [PATCH 3/3] dmaengine: at_xdmac: allow muliple dwidths when doing slave transfers Ludovic Desroches
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=20141211044220.GG16827@intel.com \
--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).