linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cubicool@gmail.com (Jeremy Moles)
To: linux-arm-kernel@lists.infradead.org
Subject: EP93XX / EDB9315A Audio Issues
Date: Wed, 10 Sep 2014 13:57:33 -0400	[thread overview]
Message-ID: <5410910D.6060201@gmail.com> (raw)

(I'm cross-posting this to the linux-arm-kernel and alsa-devel lists, as 
recommended):

I'm looking for anyone who has successfully used the EP93XX/EDB9315A 
demo board's sound infrastructure. I have been working with Hartley 
Sweeten on patching some DMA coherency mask issues (successfully), and 
while this makes the kernel stop complaining (and allows the userspace 
to "appear" to work) I never actually get any sound out of the machine 
on newer kernels.

I do, however, have an existing (binary-only) 2.6.21 kernel from the 
client where sound _IS_ functional; thus, I know the system can 
POTENTIALLY work, and that the problem is software-based.

At this point, I have a mountain of information I can provide about the 
state of my EDB9315A board, but what I'm really looking for is someone 
to connect with and/or have consult with us to get sound working on 
newer kernels with this board exactly (although other EP93XX boards 
might be similar, I'm so mistrustful of everything at this point I'm 
looking for someone else with this hardware EXACTLY).

I've tried 3.15-3.17, all with the same results. aplay/alsamixer see the 
device, appear to interact with it in a normal fashion (it even 
mutes/unmutes the device every time you touch it), but no sound is ever 
produced. It is possible, of course, the problem is in userspace (I'm 
using a custom Yocto-based image), but I'm doubtful of that.

At any rate, any help would be greatly appreciate, although i realize 
this is fringe hardware. :)

             reply	other threads:[~2014-09-10 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 17:57 Jeremy Moles [this message]
2014-11-14 15:04 ` EP93XX / EDB9315A Audio Issues Jeremy Moles

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=5410910D.6060201@gmail.com \
    --to=cubicool@gmail.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).