All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Radoslaw Szkodzinski <astralstorm@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Lynx HiLo USB DAC issues
Date: Thu, 12 Sep 2013 18:41:46 +0200	[thread overview]
Message-ID: <5231EECA.1030600@gmail.com> (raw)
In-Reply-To: <CAAmECqRfMqgVXSjuouqVzBX1FOGt79c+ueSQ1xLVFQAJ4QE6tw@mail.gmail.com>

Hi Radoslaw,

On 12.09.2013 02:43, Radoslaw Szkodzinski wrote:
> Never mind, I see the issue now. (It is late here.)
> The CLOCK_SELECTOR is read-only according to lsusb output.
> 
> Apparently uac_clock_selector_get_val fails to work, returning invalid
> pin number.
> That should not happen, but it shouldn't be called either in this
> case, as the selector is irrelevant.

Sorry, I don't follow. Given that you successfully dug into the driver
sources already, can you share a patch that makes things work for you?

The problem with the clocking framework in UAC2 is that it's quite
powerful (there are multipliers, dividers, switches etc), but I haven't
yet seen a system that actually makes uses it in more complex
applications. Hence it's not exactly easy to come up with a generic
approach of how to handle all the possible cases correctly, and how to
react on clock validity loss for instance.

Help from someone who has access to a more complex device is hence more
than welcome :)


Thanks,
Daniel

  reply	other threads:[~2013-09-12 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAmECqTLRKu8uEpX9YHY3=W5bB0ydys2oQ2pAgHs2WjsjCqUFQ@mail.gmail.com>
2013-09-12  0:01 ` Fwd: Lynx HiLo USB DAC issues Radoslaw Szkodzinski
2013-09-12  0:12   ` Radoslaw Szkodzinski
2013-09-12  0:43     ` Radoslaw Szkodzinski
2013-09-12 16:41       ` Daniel Mack [this message]
2013-09-12 17:00         ` Radoslaw Szkodzinski
2013-09-12 17:07           ` Daniel Mack

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=5231EECA.1030600@gmail.com \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=astralstorm@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.