From: Timur Tabi <timur@tabi.org>
To: eshe168 <eshe168@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
zhphsearch <zhphsearch@163.com>
Subject: Re: P1022 audio driver help!
Date: Fri, 30 May 2014 10:48:33 -0500 [thread overview]
Message-ID: <5388A851.2010508@tabi.org> (raw)
In-Reply-To: <2014053014034907812079@gmail.com>
On 05/30/2014 01:03 AM, eshe168 wrote:
> @timur
> hi,
> Audio card (wm8776) cannot work in full duplex, CPU is FSL P1022.
> The PCB design about audio card reference FSL P1022 development board,
> and palying or recording is OK separately.
> My question is whether P1022 audio driver cannot support full duplex?
I was never able to get the P1022ds audio to work in full duplex. After
trying for a few weeks, I just gave up.
If you look inside fsl_ssi.c (the main driver) you'll see this comment I
wrote:
/*
* FIXME: The documentation says that SxCCR[WL] should not be
* modified while the SSI is enabled. The only time this can
* happen is if we're trying to do simultaneous playback and
* capture in asynchronous mode. Unfortunately, I have been enable
* to get that to work at all on the P1022DS. Therefore, we don't
* bother to disable/enable the SSI when setting SxCCR[WL], because
* the SSI will stop anyway. Maybe one day, this will get fixed.
*/
(it should say "I have been unable" instead of "I have been enable")
Full duplex works fine on the MPC8610, which has the same audio
controller as the P1022, so I know the controller is physically capable
of it. I just don't know why it doesn't work on the P1022DS. I also
don't know if it's a problem with the P1022DS board or with the P1022
SOC itself.
next prev parent reply other threads:[~2014-05-30 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 6:03 P1022 audio driver help! eshe168
2014-05-30 15:48 ` Timur Tabi [this message]
2014-06-02 14:05 ` eshe168
2014-06-02 15:52 ` Timur Tabi
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=5388A851.2010508@tabi.org \
--to=timur@tabi.org \
--cc=eshe168@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=zhphsearch@163.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 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.