All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Demian Martin <demianm_1@yahoo.com>
Cc: hegge@resisty.net, alsa-devel@alsa-project.org
Subject: Re: ALSA: usb: Work around CM6631 sample
Date: Wed, 06 Mar 2013 09:43:00 +0100	[thread overview]
Message-ID: <51370194.1080808@ladisch.de> (raw)
In-Reply-To: <001f01ce19fa$6d770c80$48652580$@com>

Demian Martin wrote:
> CMedia ... told me that the chips are different

The CM6610/20 chips did not get an updated -A version, so it's possible
that the changes are just for the I²S I/Os, which should not affect the
USB interface.  Maybe the newer chip just gave them an opportunity to
update the firmware.

> there is a sequence problem between setting sample rate and sending
> the "play' command.

This sound like the interface setting problem fixed by this patch.

> Something about UAC1 method not being the same as UAC2.

But this might indicate that we need to kick the Clock Source Entity.


Regards,
Clemens

      reply	other threads:[~2013-03-06  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 23:37 ALSA: usb: Work around CM6631 sample Demian Martin
2013-03-06  8:43 ` Clemens Ladisch [this message]

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=51370194.1080808@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=demianm_1@yahoo.com \
    --cc=hegge@resisty.net \
    /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.