From: Clemens Ladisch <clemens@ladisch.de>
To: Appalayagari Sreedhar <sreecha01@gmail.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>,
Vladimir Barinov <Vladimir_Barinov@mentor.com>
Subject: Re: DM365 McBSP as Master
Date: Mon, 24 Oct 2011 20:40:07 +0200 [thread overview]
Message-ID: <4EA5B107.9090904@ladisch.de> (raw)
In-Reply-To: <CAODvfaE1Sp-=GYx=A3tM55Xn+hWTQzb4NmH+3nnn0F0jznwniA@mail.gmail.com>
Appalayagari Sreedhar wrote:
> Thank you very much. but for the tlv320aic3x codec it works.
> tlv320aic3x device is also duplex device. and also after aplay
> calling, i can succesfully open the device for my codec driver.
> could you please tell me what i am missing and also why it is working
> for the tlv320aic3x device.
There's probably some difference in the behaviour of the two drivers
regarding multiple opens. Which drivers are you using (the codecs
don't matter)?
Regards,
Clemens
next prev parent reply other threads:[~2011-10-24 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAODvfaF4f0ZrPQdR1CiFBp5=WZAkj9fQnjNPgdY15c0wYW-fkA@mail.gmail.com>
[not found] ` <4E78A059.4010300@mentor.com>
[not found] ` <CAODvfaG=uSC0J6-q+Cd6cb4Sfb1gNRoYE2UCAziKmtVKa2_qeQ@mail.gmail.com>
[not found] ` <CAODvfaEEwdPbZGz91H-F080nfPh33r8Y16aCoB83SeghaMGqbA@mail.gmail.com>
[not found] ` <4E7C3039.1090203@mentor.com>
[not found] ` <CAODvfaEMx+Jz0dYbUcPsyJ6JWKXi-_wmbXC=MsC11Jv+PUuJ1g@mail.gmail.com>
[not found] ` <4E9BF5A0.5090203@mentor.com>
2011-10-17 12:27 ` DM365 McBSP as Master Appalayagari Sreedhar
2011-10-17 12:29 ` Appalayagari Sreedhar
2011-10-17 12:47 ` Clemens Ladisch
2011-10-17 13:26 ` Appalayagari Sreedhar
2011-10-24 18:40 ` Clemens Ladisch [this message]
2011-11-30 10:39 ` Appalayagari Sreedhar
2011-11-30 13:47 ` Mark Brown
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=4EA5B107.9090904@ladisch.de \
--to=clemens@ladisch.de \
--cc=Vladimir_Barinov@mentor.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=sreecha01@gmail.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.