From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: GSoC 2014 #0 status report - Improving Allwinner SoC support
Date: Thu, 10 Jul 2014 22:39:06 +0200 [thread overview]
Message-ID: <20140710203906.GA3745@lukather> (raw)
In-Reply-To: <53BE0B4F.1090001@elopez.com.ar>
Hi,
On Thu, Jul 10, 2014 at 12:41:03AM -0300, Emilio L?pez wrote:
> Hi everyone,
>
> As some of you may know, I'm currently participating in Google
> Summer of Code under the Linux Foundation, working on a proposal
> titled "Improve Allwinner SoCs support on mainline Linux". There is
> a great quantity of devices out there that are powered by Allwinner
> processors, including but not limited to the various Cubieboards,
> OLinuXinos, STBs, Tablets and ?Mini PCs?. However, to date, support
> on mainline Linux is not yet feature complete. My proposal on
> particular focuses on DMA and analog audio on the earlier SoCs, and
> improved A23 support.
>
> The idea here is to make a weekly status report of the project. As
> we are starting mid-program, this one will be a bit different and
> I'll outline what has been worked on so far since the beginning.
>
> To date, I have been mainly working on the DMA driver for sun4i,
> sun5i and sun7i. Despite having completely different drivers on SDK
> kernels, the hardware block looks and behaves the same, so we are
> using a single driver for these three SoC families. I have sent a
> series of patches[1] as well as a follow-up v2[2], and I will keep
> iterating over it until it's accepted. I have also sent two trivial
> patches[3][4] as a side-effect.
Yep, thanks a lot for that good work.
Hopefully, it will be merged rather soon, as it looks quite nice
already.
> The main challenges while writing this driver can be summarized as a
> lack of documentation. First of all, it took me a bit to get to know
> DMAEngine. As there is not much documentation on it, most of my
> learning took place by reading pre-existing drivers and consulting
> with my mentor. Secondly, as the Allwinner documentation is mostly a
> register list with bitfield details, I also had to read the SDK
> drivers and do some trial and error testing to discover magic values
> and understand others.
I feel your pain :)
> 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?
> 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?
> To give some closure to this status report, I'd like to thank Maxime
> for his mentoring so far, Ezequiel for letting me pick his brain,
> and the Linux Foundation and Google for giving me this opportunity,
> as well as everyone on the kernel and sunxi communities who have
> come forward to review and test patches. You can expect a new report
> soon, in about a week's time or less.
Keep up the good work.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140710/5b8b35cc/attachment.sig>
next prev parent reply other threads:[~2014-07-10 20:39 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 [this message]
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
[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=20140710203906.GA3745@lukather \
--to=maxime.ripard@free-electrons.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