From: Muni Sekhar <munisekharrms@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
linux-usb@vger.kernel.org, linux-sound@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: USB sound card issues
Date: Tue, 15 Jun 2021 12:30:45 +0530 [thread overview]
Message-ID: <CAHhAz+iOFda+T3=ri2o8UhNR1L1KVdKJUYABS8djijqvhsn3JQ@mail.gmail.com> (raw)
In-Reply-To: <27987.1623737660@turing-police>
On Tue, Jun 15, 2021 at 11:44 AM Valdis Klētnieks
<valdis.kletnieks@vt.edu> wrote:
>
> On Sat, 12 Jun 2021 16:45:00 +0530, Muni Sekhar said:
>
> > > And if it's configurable for multiple formats, was it set for the correct one?
> > Is there a way to verify was it set for the correct one or not?
>
> arecord -v gives what it thinks the setup is.
>
> > > Does the record die immediately, or hang for a few seconds and timeout?
> > What is the difference between these two ways?
>
> An immediate failure is usually related to a "Can't do it" situation where the
> USB interaction to configure the device has failed, while a timeout usually
> indicates that the configuration at least *claimed* to succeed, but is failing
> to properly transfer valid data.
>
> > For my hardware, I noticed that it hangs for a few seconds and gives EIO (arecord:
> > pcm_read:2032: read error: Input/output error).
>
> Given that the usbmon output ran to several megabytes, that's tending to
> point at "the card was returning lots of packets, but they weren't actually the
> format/data that arecord was expecting.
So, is it a USB card issue?
--
Thanks,
Sekhar
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2021-06-15 7:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 10:50 USB sound card issues Muni Sekhar
2021-06-08 11:14 ` Greg KH
2021-06-08 12:14 ` Muni Sekhar
2021-06-08 12:31 ` Greg KH
2021-06-08 12:45 ` Muni Sekhar
2021-06-08 13:03 ` Greg KH
2021-06-11 23:46 ` Valdis Klētnieks
2021-06-12 11:15 ` Muni Sekhar
2021-06-15 6:14 ` Valdis Klētnieks
2021-06-15 7:00 ` Muni Sekhar [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='CAHhAz+iOFda+T3=ri2o8UhNR1L1KVdKJUYABS8djijqvhsn3JQ@mail.gmail.com' \
--to=munisekharrms@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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).