Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: marve <marve@xs4all.nl>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: problem with the driver for ALC3260 sound chip
Date: Sat, 26 Nov 2016 09:21:07 +0100	[thread overview]
Message-ID: <s5h37ie6498.wl-tiwai@suse.de> (raw)
In-Reply-To: <763c7ae9-9f12-484d-e1ec-0bc7a09cb066@xs4all.nl>

On Fri, 25 Nov 2016 22:22:59 +0100,
marve wrote:
> 
> 
> On 11/25/2016 06:08 PM, Takashi Iwai wrote:
> > On Wed, 23 Nov 2016 21:42:26 +0100,
> > marve wrote:
> >> Dear all,
> >>
> >> Here a rephrase of my issue with TOSLINK SPDIF output of my Dell XPS One
> >> 2710 system running Linux.
> >>
> >>
> >> First: I have tried other hardware with my DTS receiver and the receiver
> >> worked fine. Also I have checked the HDMI output of my computer, also
> >> working!
> >>
> >> Second: The SPDIF output worked fine on a Windows 7 installation with
> >> PCM and DTS. I stopped using Windows privately.
> >>
> >> Most success I got with debugging the SPDIF TOSLINK is:
> >> - With the HDA Intel sound cards Jack Retasking tool:
> >>      - Check Showing unconnected pins. Actually, the TOSLINK is
> >> connected but shows "not connected" in the tool.
> >>      - Manually override Pin ID 0x1e
> >>      - Select "SPDIF Out" and "Apply Now"
> > You're sure that this pin is correct?  I mean, did you get *any*
> > signal from the SPDIF I/O by enabling this pin?
> >
>  No signal at all from the SPDIF Toslink port! The reason trying this
> pin is that when overridden, it shows "SPDIF Out".

If so, the pin can be simply wrong.  Usually when a PCM stream starts
and "IEC958 Playback Switch" is on, the signal comes up.

You need to figure out which pin is connected to SPDIF.
(And note that it's not necessarily the Realtek codec that is
 connected to SPDIF, although it's very likely.)

Or, there can be some vendor-specific verb, GPIO, vref or whatever
non-standard control for enabling the SPDIF in addition.

Both above can be figured out only by the h/w owner -- or maybe better
to ask the hardware vendor about it.


Takashi

> >> - Then with PulseAudio Volume Control:
> >>     -  In the Configuration Tab, select "Profile: Digital Stereo
> >> (IEC958) Output"
> >>     -  In the Output Devices "Digital Output (S/PDIF)" appears and is
> >> the only option and in the advanced tab PCM, DTS, AC3, MPEG, EAC3, AAC
> >> are selected
> >>
> >>  - I check if in alsamixer tool that the SPDIF channel is unmuted
> >>
> >> When I play a sound, the vumeter of PulseAudio Volume Control does
> >> react, see png attachment (https://postimg.org/image/5tu4rax9t/), but my
> >> external DTS receiver doesn't get input!
> > First off, you should try the normal audio PCM stream instead of DTS
> > or such.  It's possible that the SPDIF status bits aren't properly set
> > and the receiver doesn't accept the non-audio signals.
>  Ok, I deselected all other streams except PCM, no signal.. (Will do
> this in future tests).
> 
> > And, as a primary testing, please test with aplay.  You can pass
> > -Dspdif or -Dspdif:1 option to transmit over the SPDIF device.
>  I was able to run "aplay -Dspdif" without errors. I also checked in
> another terminal if the alsamixer showed the s/pdif channels unmuted.
> They are unmuted, but I didn't get a signal to my audio receiver. 
> 
> "aplay -Dspdif:1" didn't work: "Cannot find card".
> > Last but not least, check the IEC958 status bits of the assigned PCM.
> > You can use iecset program in alsa-utils for checking / setting the
> > bits.
> >
> iecset -x shows:
> 
> AES0=0x05,AES1=0x82,AES2=0x00,AES3=0x00
> 
> Best,
> Marijn
> > Takashi
> >
> 

      reply	other threads:[~2016-11-26  8:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 20:42 problem with the driver for ALC3260 sound chip marve
2016-11-25 17:08 ` Takashi Iwai
2016-11-25 21:22   ` marve
2016-11-26  8:21     ` Takashi Iwai [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=s5h37ie6498.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=marve@xs4all.nl \
    /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