From: emilio@elopez.com.ar (Emilio López)
To: linux-arm-kernel@lists.infradead.org
Subject: GSoC 2014 #0 status report - Improving Allwinner SoC support
Date: Sat, 12 Jul 2014 01:17:00 -0300 [thread overview]
Message-ID: <53C0B6BC.80201@elopez.com.ar> (raw)
In-Reply-To: <20140710203906.GA3745@lukather>
Hi,
El 10/07/14 17:39, Maxime Ripard escribi?:
>> Lately, I have also been working on the audio part, now that I have
>> a working DMA driver. After implementing cyclic DMA transfers and
>> some clock code, and armed with a Buildroot image with mpg123 and an
>> OpenBSD release track[5] in mp3 format, I've been trying to get some
>> sound out of my Cubietruck's headphone jack, but without much
>> success so far. I have verified my userspace stack and hardware by
>> running these same binaries on top of the linux-sunxi 3.4 kernel,
>> and it worked fine. I have since then been dumping relevant
>> registers with devmem and comparing them, resolving issues as I see
>> them - hopefully this will yield some audible results.
>
> What have you been working on? A new driver from scratch, tried to
> take Allwinner's code and then cleant it up, or used the recently
> published driver Jon made?
I've been working on top of Jon's codec patches. Seeing that the last
series Jon published on his github produces some sound, I got a fresh
copy of it today, and with some changes on DMAEngine, it's playing nicely.
As cyclic transactions are special (eg, they don't become empty) I
rewrote the cyclic support Jon had, making it issue subsequent transfers
directly from the interrupt request, and minimizing the number of times
this needs to be done. If we use the half done interrupt, we can get
away with one hardware programming per two periods.
It's rather late now and I still need to clean up the code a bit, but
I'll push a branch with these changes on my repo during the weekend.
>> Interestingly enough, Allwinner themselves do not seem to be using
>> cyclic DMA transfers on their driver[6]. I hope this is not a sign
>> of a hardware bug that's not documented.
>
> So they just implement a cyclic-like behaviour in software?
Yep, they have this code to cycle through the buffer
https://github.com/linux-sunxi/linux-sunxi/blob/sunxi-3.4/sound/soc/sunxi/sunxi-codec.c#L648
Cheers!
Emilio
next prev parent reply other threads:[~2014-07-12 4:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 3:41 GSoC 2014 #0 status report - Improving Allwinner SoC support Emilio López
2014-07-10 10:46 ` [linux-sunxi] " Hans de Goede
2014-07-10 12:32 ` jonsmirl at gmail.com
2014-07-10 12:38 ` jonsmirl at gmail.com
2014-07-10 16:13 ` jonsmirl at gmail.com
2014-07-10 16:23 ` jonsmirl at gmail.com
2014-07-10 20:39 ` Maxime Ripard
2014-07-10 22:40 ` [linux-sunxi] " jonsmirl at gmail.com
2014-07-10 22:55 ` Russell King - ARM Linux
2014-07-12 4:17 ` Emilio López [this message]
[not found] ` <53CAC9ED.9080302@elopez.com.ar>
2014-07-20 4:18 ` [linux-sunxi] GSoC 2014 #1 " Chen-Yu Tsai
2014-07-22 10:22 ` Chen-Yu Tsai
2014-07-22 13:11 ` jonsmirl at gmail.com
2014-07-22 13:17 ` Chen-Yu Tsai
2014-07-23 5:15 ` Chris Moore
2014-07-23 5:19 ` Chen-Yu Tsai
2016-03-12 13:41 ` jonsmirl at gmail.com
2014-07-20 9:06 ` Julian Calaby
[not found] ` <53DFFA5B.1040006@elopez.com.ar>
2014-08-07 11:33 ` GSoC 2014 #2 " Maxime Ripard
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=53C0B6BC.80201@elopez.com.ar \
--to=emilio@elopez.com.ar \
--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 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.