From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Aurélien <aurelien@ap2c.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Garbage returned while reading unused S/PDIF, A CM106 like sound card
Date: Wed, 5 Jul 2023 13:27:02 -0300 [thread overview]
Message-ID: <ZKWZ1l+fIBlEHELJ@geday> (raw)
In-Reply-To: <5962046.lOV4Wx5bFT@antimony.ap2c.org>
On Tue, Jul 04, 2023 at 08:06:04PM +0200, Aurélien wrote:
> Hello,
Hi Aurélien!
>
> I encounter troubles while using S/PDIF input on an CM106 like sound card
> (vendor 0x0d8c, device 0x0102) when the remote device which is connected by S/
> PDIF to the sound card is powered off.
> In that case garbage data are reading from the S/PDIF rather than.. nothing
>
> It is really boring since this S/PDIF input is connected to the output
> speakers and once the remote deviced is powered off it emits a really
> disturbing sound.
> Since there is no input on the S/PDIF I guess that it could be a driver bug?
> If it's an hardware bug (I don't encounter the problem under windows..) is it
> possible to make a hack in order to distinguish between real data and noise on
> the S/PDIF input?
>
> Unfortunately this test is performed on an embedded device which runs linux
> 5.16.17-sun50iw6. I don't know if this problem still occurs with newer alsa
> version.
This looks like a vendor (downstream) kernel. ALSA Project does not
accept bug reports for vendor kernels. You must try to reproduce your
issue with the latest mainline kernel.
Thanks,
Geraldo Nascimento
>
> Thank you in advance for your help.
> Regards,
>
> Aurélien
>
>
prev parent reply other threads:[~2023-07-05 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 18:06 Garbage returned while reading unused S/PDIF, A CM106 like sound card Aurélien
2023-07-05 16:27 ` Geraldo Nascimento [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=ZKWZ1l+fIBlEHELJ@geday \
--to=geraldogabriel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=aurelien@ap2c.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox