From: Matthias Reichl <hias@horus.com>
To: Vinod Koul <vinod.koul@intel.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Eric Anholt <eric@anholt.net>
Cc: Martin Sperl <kernel@martin.sperl.org>,
Clive Messer <clive.messer@digitaldreamtime.co.uk>,
dmaengine@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] dmaengine: bcm2835: Cyclic DMA fixes
Date: Thu, 9 Jun 2016 13:41:42 +0200 [thread overview]
Message-ID: <1465472504-10191-1-git-send-email-hias@horus.com> (raw)
In downstream Raspberry Pi kernel we noticed that audio didn't work
as expected, we got stuttering and overruns/underruns. Here's the
link to the original discussion on GitHub:
https://github.com/raspberrypi/linux/issues/1517
This issue is caused by a small bug in the period-splitting-code
and fixed by the first patch.
The second patch, avoiding very small chunks, is mainly a precaution.
While small chunks are not known to have caused any problems so far
they have the potentical to cause very hard to track down issues.
So better avoid such situations in the first place.
Matthias Reichl (2):
dmaengine: bcm2835: Fix cyclic DMA period splitting
dmaengine: bcm2835: Avoid splitting periods into very small chunks
drivers/dma/bcm2835-dma.c | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
--
2.1.4
next reply other threads:[~2016-06-09 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 11:41 Matthias Reichl [this message]
2016-06-09 11:41 ` [PATCH 1/2] dmaengine: bcm2835: Fix cyclic DMA period splitting Matthias Reichl
2016-06-14 4:49 ` Eric Anholt
2016-06-09 11:41 ` [PATCH 2/2] dmaengine: bcm2835: Avoid splitting periods into very small chunks Matthias Reichl
2016-06-14 5:06 ` Eric Anholt
2016-06-19 10:39 ` Matthias Reichl
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=1465472504-10191-1-git-send-email-hias@horus.com \
--to=hias@horus.com \
--cc=clive.messer@digitaldreamtime.co.uk \
--cc=dmaengine@vger.kernel.org \
--cc=eric@anholt.net \
--cc=kernel@martin.sperl.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=swarren@wwwdotorg.org \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®