From: Alexander Kochetkov <al.kochet@gmail.com>
To: Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Caesar Wang <wxt@rock-chips.com>,
Doug Anderson <dianders@chromium.org>,
linux-rockchip@lists.infradead.org,
Heiko Stuebner <heiko@sntech.de>
Subject: Cleanups and improvenments for pl330 v3
Date: Thu, 10 Mar 2016 14:02:41 +0300 [thread overview]
Message-ID: <1457607764-30495-1-git-send-email-al.kochet@gmail.com> (raw)
In-Reply-To: <1455798674-10186-1-git-send-email-al.kochet@gmail.com>
Hello,
Here is v2 series of pl330 fixes. It is rebased again linux next-20160310.
The patches were tested on rk3188 radxarock.
>8 march 2016 г., * 6:03, Vinod Koul <vinod.koul@intel.com> *:
>Overall this series looks okay, but can someone test this. I would not like
>pl330 to be roken again
Bartlomiej, could you please test the patches on Samsung Exynos4412?
Dinh, could you please test the patches on SoCFPGA?
So I will add your name as Tested-by.
> 10 march 2016 г., * 8:55, Caesar Wang <wxt@rock-chips.com> *:
> The above series patches will solve the I2S clic problem, right?
The patch "dmaengine: pl330: make cyclic transfer free runnable" fixes
sound click problem. So if you noticed sound clicks on your board,
please test the patches.
The patch "dmaengine: pl330: don't emit code for one iteration loop"
is simple improvement allows to save some bytes of pl330 MicroCode
buffer.
The patch "dmaengine: pl330: cleanup quirk pass code" is improvement
intended to hide struct pl330_dmac from low-level functions.
It partially revert changes introduced by 271e1b86e691 "dmaengine:
pl330: add quirk for broken no flushp".
[PATCH 1/3 v3] dmaengine: pl330: cleanup quirk pass code
[PATCH 2/3 v3] dmaengine: pl330: don't emit code for one iteration loop
[PATCH 3/3 v3] dmaengine: pl330: make cyclic transfer free runnable
next prev parent reply other threads:[~2016-03-10 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 12:31 Cleanups and improvenments for pl330 Alexander Kochetkov
2016-02-18 12:31 ` [PATCH 1/4] dmaengine: pl330: cleanup quirk pass code Alexander Kochetkov
2016-02-18 12:31 ` [PATCH 2/4] dmaengine: pl330: cleanup brst_len usage Alexander Kochetkov
2016-02-18 12:31 ` [PATCH 3/4] dmaengine: pl330: don't emit code for one iteration loop Alexander Kochetkov
2016-02-18 12:31 ` [PATCH 4/4] dmaengine: pl330: make cyclic transfer free runnable Alexander Kochetkov
2016-03-08 3:03 ` Cleanups and improvenments for pl330 Vinod Koul
2016-03-10 10:57 ` [PATCH 1/3 v2] dmaengine: pl330: cleanup quirk pass code Alexander Kochetkov
2016-03-10 10:57 ` [PATCH 2/3 v2] dmaengine: pl330: don't emit code for one iteration loop Alexander Kochetkov
2016-03-10 10:57 ` [PATCH 3/3 v2] dmaengine: pl330: make cyclic transfer free runnable Alexander Kochetkov
2016-03-10 11:02 ` Alexander Kochetkov [this message]
2016-03-10 11:02 ` [PATCH 1/3 v3] dmaengine: pl330: cleanup quirk pass code Alexander Kochetkov
2016-03-10 11:02 ` [PATCH 2/3 v3] dmaengine: pl330: don't emit code for one iteration loop Alexander Kochetkov
2016-03-10 11:02 ` [PATCH 3/3 v3] dmaengine: pl330: make cyclic transfer free runnable Alexander Kochetkov
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=1457607764-30495-1-git-send-email-al.kochet@gmail.com \
--to=al.kochet@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dianders@chromium.org \
--cc=dmaengine@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=vinod.koul@intel.com \
--cc=wxt@rock-chips.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).