Skip to contentSkip to conversation

ALSA: HDA VIA: patch series

PATCH In review Logan Li 3 participants 14 messages Oct 10, 2009 – Oct 16, 2009

lore
Share & tools
lore

Logan Li

author
#0 lore raw

cover ALSA: HDA VIA: patch series

Following patch series mainly includes:
- support VT1718S, VT2002P, VT1812S, VT1716S, ...
- support smart 5.1
- add jack detection for VT1708
- power saving functions

#1 lore raw
Quoted 5 lines · Logan Li

Following patch series mainly includes:
 - support VT1718S, VT2002P, VT1812S, VT1716S, ...
 - support smart 5.1
 - add jack detection for VT1708
 - power saving functions

OK, this patch set fixes the problem with being unable to open the mixer, and it looks like the SPDIF digital converter entries are being enabled automatically so I get a signal indication on my receiver. Still not getting any actual SPDIF audio through the receiver though, unfortunately. Also it appears that the 48000 fixed sample rate limit for SPDIF outputs is still there for the newly added codec types, I'd say it should be removed for them as well..

#2 lore raw
In reply to Logan Li

At Sat, 10 Oct 2009 19:07:09 +0800,

Quoted 6 lines · Logan Li

Following patch series mainly includes:
- support VT1718S, VT2002P, VT1812S, VT1716S, ...
- support smart 5.1
- add jack detection for VT1708
- power saving functions

Thanks for the patches. They are all well formatted now.

I applied your patches except for 17,
ALSA: HDA VIA: Add 2nd S/PDIF out for VT1708S and VT1702
as Robert reported a regression.

This is likely because of the behavior change by this patch. Now the second SPDIF has to be specified manually with the explicit substream number. This itself is fine, but I see the problem with pulseaudio, for example. There is no good way to specify this substream automatically for PA with some symbols like "spdif" or "hdmi".

This is basically a problem of the current ALSA core and HD-audio core implementation. So, we should solve all together.

On most machines, it's not too big deal to have it the secondary digital as a slave. If this really matters, we can add another hint to make the individual digital substreams conditionally.

Anyway, please check the latest sound GIT tree (or alsa-driver snapshot) whether it works. I only tested the compilation, so far.

thanks,

Takashi

#3 lore raw
Quoted 15 lines · Takashi Iwai

At Sat, 10 Oct 2009 19:07:09 +0800,

Quoted 6 lines · Logan Li

Following patch series mainly includes:
 - support VT1718S, VT2002P, VT1812S, VT1716S, ...
 - support smart 5.1
 - add jack detection for VT1708
 - power saving functions

Thanks for the patches.  They are all well formatted now.

I applied your patches except for 17,
       ALSA: HDA VIA: Add 2nd S/PDIF out for VT1708S and VT1702 as Robert reported a regression.

Quoted 8 lines

This is likely because of the behavior change by this patch.  Now the second SPDIF has to be specified manually with the explicit substream number.  This itself is fine, but I see the problem with pulseaudio, for example.  There is no good way to specify this substream automatically for PA with some symbols like "spdif" or "hdmi".

This is basically a problem of the current ALSA core and HD-audio core implementation.  So, we should solve all together.

Actually, the latest posted version didn't have the mixer problem I had before (I haven't looked in detail at what was different). But I agree using a different substream for a different output isn't ideal since there's no way for software to detect that this is the case. Can it be a separate PCM like hw:0,2 or something?

Hopefully VIA will also look into the SPDIF no-output problem I have with VT1828S..

Quoted 13 lines

On most machines, it's not too big deal to have it the secondary digital as a slave.  If this really matters, we can add another hint to make the individual digital substreams conditionally.

Anyway, please check the latest sound GIT tree (or alsa-driver snapshot) whether it works.  I only tested the compilation, so far.

thanks,

Takashi

#4 lore raw

At Sun, 11 Oct 2009 10:56:48 -0600,

Quoted 23 lines · Robert Hancock
Quoted 21 lines · Takashi Iwai

At Sat, 10 Oct 2009 19:07:09 +0800,

Quoted 6 lines · Logan Li

Following patch series mainly includes:
 - support VT1718S, VT2002P, VT1812S, VT1716S, ...
 - support smart 5.1
 - add jack detection for VT1708
 - power saving functions

Thanks for the patches.  They are all well formatted now.

I applied your patches except for 17,
       ALSA: HDA VIA: Add 2nd S/PDIF out for VT1708S and VT1702 as Robert reported a regression.

This is likely because of the behavior change by this patch.  Now the second SPDIF has to be specified manually with the explicit substream number.  This itself is fine, but I see the problem with pulseaudio, for example.  There is no good way to specify this substream automatically for PA with some symbols like "spdif" or "hdmi".

Quoted 8 lines
Quoted 2 lines

This is basically a problem of the current ALSA core and HD-audio core implementation.  So, we should solve all together.

Actually, the latest posted version didn't have the mixer problem I had before (I haven't looked in detail at what was different). But I agree using a different substream for a different output isn't ideal since there's no way for software to detect that this is the case. Can it be a separate PCM like hw:0,2 or something?

It would work like hw:0,1,1. But, this is exactly what I mentioned in the above. The secondary SPDIF isn't specified as an intuitively selectable PCM device.

Quoted 2 lines

Hopefully VIA will also look into the SPDIF no-output problem I have with VT1828S..

What is the problem, specifically?

thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#5 lore raw
Quoted 34 lines · Takashi Iwai

At Sun, 11 Oct 2009 10:56:48 -0600,

Quoted 23 lines · Robert Hancock
Quoted 21 lines · Takashi Iwai

At Sat, 10 Oct 2009 19:07:09 +0800,

Quoted 6 lines · Logan Li

Following patch series mainly includes:
- support VT1718S, VT2002P, VT1812S, VT1716S, ...
- support smart 5.1
- add jack detection for VT1708
- power saving functions

Thanks for the patches. They are all well formatted now.

I applied your patches except for 17,
ALSA: HDA VIA: Add 2nd S/PDIF out for VT1708S and VT1702
as Robert reported a regression.

This is likely because of the behavior change by this patch. Now the second SPDIF has to be specified manually with the explicit substream number. This itself is fine, but I see the problem with pulseaudio, for example. There is no good way to specify this substream automatically for PA with some symbols like "spdif" or "hdmi".

Quoted 8 lines
Quoted 2 lines

This is basically a problem of the current ALSA core and HD-audio core implementation. So, we should solve all together.

Actually, the latest posted version didn't have the mixer problem I had before (I haven't looked in detail at what was different). But I agree using a different substream for a different output isn't ideal since there's no way for software to detect that this is the case. Can it be a separate PCM like hw:0,2 or something?

Quoted 3 lines

It would work like hw:0,1,1. But, this is exactly what I mentioned in the above. The secondary SPDIF isn't specified as an intuitively selectable PCM device.

Well, if it was its own subdevice like hw:0,2 it would have some hope of being detected by HAL, PulseAudio, etc. If it's just a substream then I don't think that software can actually tell it's a separate output and not just a HW mixing-type stream, etc.

Quoted 5 lines
Quoted 3 lines

Hopefully VIA will also look into the SPDIF no-output problem I have with VT1828S..

What is the problem, specifically?

With the latest patch I do get the optical output lighting up and the receiver detects a PCM signal, but it seems to be just silence coming through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

#6 lore raw

At Sun, 11 Oct 2009 13:51:28 -0600,

Quoted 36 lines · Robert Hancock
Quoted 34 lines · Takashi Iwai

At Sun, 11 Oct 2009 10:56:48 -0600,

Quoted 31 lines · Robert Hancock
Quoted 15 lines · Takashi Iwai

At Sat, 10 Oct 2009 19:07:09 +0800,

Quoted 6 lines · Logan Li

Following patch series mainly includes:
- support VT1718S, VT2002P, VT1812S, VT1716S, ...
- support smart 5.1
- add jack detection for VT1708
- power saving functions

Thanks for the patches. They are all well formatted now.

I applied your patches except for 17,
ALSA: HDA VIA: Add 2nd S/PDIF out for VT1708S and VT1702
as Robert reported a regression.

Quoted 8 lines

This is likely because of the behavior change by this patch. Now the second SPDIF has to be specified manually with the explicit substream number. This itself is fine, but I see the problem with pulseaudio, for example. There is no good way to specify this substream automatically for PA with some symbols like "spdif" or "hdmi".

This is basically a problem of the current ALSA core and HD-audio core implementation. So, we should solve all together.

Actually, the latest posted version didn't have the mixer problem I had before (I haven't looked in detail at what was different). But I agree using a different substream for a different output isn't ideal since there's no way for software to detect that this is the case. Can it be a separate PCM like hw:0,2 or something?

Quoted 8 lines
Quoted 3 lines

It would work like hw:0,1,1. But, this is exactly what I mentioned in the above. The secondary SPDIF isn't specified as an intuitively selectable PCM device.

Well, if it was its own subdevice like hw:0,2 it would have some hope of being detected by HAL, PulseAudio, etc. If it's just a substream then I don't think that software can actually tell it's a separate output and not just a HW mixing-type stream, etc.

Right, that's the missing information.

Quoted 9 lines
Quoted 4 lines
Quoted 2 lines

Hopefully VIA will also look into the SPDIF no-output problem I have with VT1828S..

What is the problem, specifically?

With the latest patch I do get the optical output lighting up and the receiver detects a PCM signal, but it seems to be just silence coming through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

You can fiddle with hda-verb to issue digital-converter verbs. Possibly you need to flip the digital-enable bit to send the values...

thanks,

Takashi

#7 lore raw
Quoted 54 lines · Takashi Iwai

At Sun, 11 Oct 2009 13:51:28 -0600,

Quoted 36 lines · Robert Hancock
Quoted 34 lines · Takashi Iwai

At Sun, 11 Oct 2009 10:56:48 -0600,

Quoted 31 lines · Robert Hancock
Quoted 15 lines · Takashi Iwai

At Sat, 10 Oct 2009 19:07:09 +0800,

Quoted 6 lines · Logan Li

Following patch series mainly includes:
  - support VT1718S, VT2002P, VT1812S, VT1716S, ...
  - support smart 5.1
  - add jack detection for VT1708
  - power saving functions

Thanks for the patches.  They are all well formatted now.

I applied your patches except for 17,
        ALSA: HDA VIA: Add 2nd S/PDIF out for VT1708S and VT1702 as Robert reported a regression.

Quoted 8 lines

This is likely because of the behavior change by this patch.  Now the second SPDIF has to be specified manually with the explicit substream number.  This itself is fine, but I see the problem with pulseaudio, for example.  There is no good way to specify this substream automatically for PA with some symbols like "spdif" or "hdmi".

This is basically a problem of the current ALSA core and HD-audio core implementation.  So, we should solve all together.

Actually, the latest posted version didn't have the mixer problem I had before (I haven't looked in detail at what was different). But I agree using a different substream for a different output isn't ideal since there's no way for software to detect that this is the case. Can it be a separate PCM like hw:0,2 or something?

Quoted 8 lines
Quoted 3 lines

It would work like hw:0,1,1.  But, this is exactly what I mentioned in the above.  The secondary SPDIF isn't specified as an intuitively selectable PCM device.

Well, if it was its own subdevice like hw:0,2 it would have some hope of being detected by HAL, PulseAudio, etc. If it's just a substream then I don't think that software can actually tell it's a separate output and not just a HW mixing-type stream, etc.

Right, that's the missing information.

Quoted 5 lines
Quoted 4 lines
Quoted 2 lines

Hopefully VIA will also look into the SPDIF no-output problem I have with VT1828S..

What is the problem, specifically?

Quoted 7 lines
Quoted 4 lines

With the latest patch I do get the optical output lighting up and the receiver detects a PCM signal, but it seems to be just silence coming through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

You can fiddle with hda-verb to issue digital-converter verbs. Possibly you need to flip the digital-enable bit to send the values...

Well, I think I tried all combinations of the flags on the digital converter in hda_analyzer without any luck. I'm assuming it's something else (presumably codec-specific) that hda_analyzer doesn't know about..

#8 lore raw
Quoted 84 lines

-----Original Message-----
From: Robert Hancock [mailto:[email protected]]
Sent: Tuesday, October 13, 2009 10:41 AM
To: Takashi Iwai
Cc: Logan Li; [email protected]; Lydia Wang; Harald Welte
Subject: Re: [PATCH 0/30] ALSA: HDA VIA: patch series

Quoted 8 lines · Takashi Iwai

At Sun, 11 Oct 2009 13:51:28 -0600,

Quoted 6 lines · Robert Hancock
Quoted 4 lines · Takashi Iwai

At Sun, 11 Oct 2009 10:56:48 -0600,

Quoted 2 lines · Robert Hancock

On Sun, Oct 11, 2009 at 10:18 AM, Takashi

Quoted 9 lines · Iwai
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

At Sat, 10 Oct 2009 19:07:09 +0800,

Quoted 6 lines · Logan Li

Following patch series mainly includes:
  - support VT1718S, VT2002P, VT1812S, VT1716S, ...
  - support smart 5.1
  - add jack detection for VT1708
  - power saving functions

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

Thanks for the patches.  They are all well formatted now.

I applied your patches except for 17,
        ALSA: HDA VIA: Add 2nd S/PDIF out for VT1708S

and VT1702

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

as Robert reported a regression.

This is likely because of the behavior change by this

patch.  Now

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

the second SPDIF has to be specified manually with the explicit substream number.  This itself is fine, but I see the

problem with

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

pulseaudio, for example.  There is no good way to

specify this substream

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

automatically for PA with some symbols like "spdif" or "hdmi".

This is basically a problem of the current ALSA core

and HD-audio core

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

implementation.  So, we should solve all together.

Actually, the latest posted version didn't have the

mixer problem I

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

had before (I haven't looked in detail at what was

different). But I

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

agree using a different substream for a different

output isn't ideal

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

since there's no way for software to detect that this

is the case. Can

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

it be a separate PCM like hw:0,2 or something?

It would work like hw:0,1,1.  But, this is exactly what

I mentioned in

Quoted 4 lines
Quoted 4 lines
Quoted 2 lines

the above.  The secondary SPDIF isn't specified as an intuitively selectable PCM device.

Well, if it was its own subdevice like hw:0,2 it would

have some hope of

Quoted 1 line
Quoted 1 line

being detected by HAL, PulseAudio, etc. If it's just a

substream then I

Quoted 1 line
Quoted 1 line

don't think that software can actually tell it's a

separate output and

Quoted 5 lines
Quoted 1 line

not just a HW mixing-type stream, etc.

Right, that's the missing information.

Quoted 1 line
Quoted 1 line
Quoted 1 line

Hopefully VIA will also look into the SPDIF no-output

problem I have

Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

with VT1828S..

What is the problem, specifically?

With the latest patch I do get the optical output lighting

up and the

Quoted 1 line
Quoted 1 line

receiver detects a PCM signal, but it seems to be just

silence coming

Quoted 3 lines
Quoted 2 lines

through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

Quoted 9 lines
Quoted 2 lines

You can fiddle with hda-verb to issue digital-converter verbs. Possibly you need to flip the digital-enable bit to send

the values...

Well, I think I tried all combinations of the flags on the digital converter in hda_analyzer without any luck. I'm assuming it's something else (presumably codec-specific) that hda_analyzer doesn't know about..

Hi, Robert
We cannot duplicate bug of SPDIF Out cannot work on VT1828S board. You said it's fine in Windows, right?
About the 48k limit, I'll send a patch to remove it later, thank you for review!

Hi, Takashi
So need I modify 2nd S/PDIF as separate PCM?

#9 lore raw

At Tue, 13 Oct 2009 17:40:48 +0800,

Quoted 95 lines · <[email protected]> wrote:
Quoted 85 lines

-----Original Message-----
From: Robert Hancock [mailto:[email protected]]
Sent: Tuesday, October 13, 2009 10:41 AM
To: Takashi Iwai
Cc: Logan Li; [email protected]; Lydia Wang; Harald Welte
Subject: Re: [PATCH 0/30] ALSA: HDA VIA: patch series

Quoted 8 lines · Takashi Iwai

At Sun, 11 Oct 2009 13:51:28 -0600,

Quoted 6 lines · Robert Hancock
Quoted 4 lines · Takashi Iwai

At Sun, 11 Oct 2009 10:56:48 -0600,

Quoted 2 lines · Robert Hancock

On Sun, Oct 11, 2009 at 10:18 AM, Takashi

Quoted 9 lines · Iwai
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

At Sat, 10 Oct 2009 19:07:09 +0800,

Quoted 6 lines · Logan Li

Following patch series mainly includes:
  - support VT1718S, VT2002P, VT1812S, VT1716S, ...
  - support smart 5.1
  - add jack detection for VT1708
  - power saving functions

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

Thanks for the patches.  They are all well formatted now.

I applied your patches except for 17,
        ALSA: HDA VIA: Add 2nd S/PDIF out for VT1708S

and VT1702

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

as Robert reported a regression.

This is likely because of the behavior change by this

patch.  Now

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

the second SPDIF has to be specified manually with the explicit substream number.  This itself is fine, but I see the

problem with

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

pulseaudio, for example.  There is no good way to

specify this substream

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

automatically for PA with some symbols like "spdif" or "hdmi".

This is basically a problem of the current ALSA core

and HD-audio core

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

implementation.  So, we should solve all together.

Actually, the latest posted version didn't have the

mixer problem I

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

had before (I haven't looked in detail at what was

different). But I

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

agree using a different substream for a different

output isn't ideal

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

since there's no way for software to detect that this

is the case. Can

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

it be a separate PCM like hw:0,2 or something?

It would work like hw:0,1,1.  But, this is exactly what

I mentioned in

Quoted 4 lines
Quoted 4 lines
Quoted 2 lines

the above.  The secondary SPDIF isn't specified as an intuitively selectable PCM device.

Well, if it was its own subdevice like hw:0,2 it would

have some hope of

Quoted 1 line
Quoted 1 line

being detected by HAL, PulseAudio, etc. If it's just a

substream then I

Quoted 1 line
Quoted 1 line

don't think that software can actually tell it's a

separate output and

Quoted 5 lines
Quoted 1 line

not just a HW mixing-type stream, etc.

Right, that's the missing information.

Quoted 1 line
Quoted 1 line
Quoted 1 line

Hopefully VIA will also look into the SPDIF no-output

problem I have

Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

with VT1828S..

What is the problem, specifically?

With the latest patch I do get the optical output lighting

up and the

Quoted 1 line
Quoted 1 line

receiver detects a PCM signal, but it seems to be just

silence coming

Quoted 3 lines
Quoted 2 lines

through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

Quoted 9 lines
Quoted 2 lines

You can fiddle with hda-verb to issue digital-converter verbs. Possibly you need to flip the digital-enable bit to send

the values...

Well, I think I tried all combinations of the flags on the digital converter in hda_analyzer without any luck. I'm assuming it's something else (presumably codec-specific) that hda_analyzer doesn't know about..

Quoted 7 lines

Hi, Robert
We cannot duplicate bug of SPDIF Out cannot work on VT1828S board. You said it's fine in Windows, right?
About the 48k limit, I'll send a patch to remove it later, thank you for review!

Hi, Takashi
So need I modify 2nd S/PDIF as separate PCM?

Well, currently the individual secondary SPDIF is a basic problem, and isn't so easily solvable in the codec-specific way.
We can have PCM substreams, but it's not exposed explicitly as really individual substreams, not the mixed one. So, this is a mixed issue between the driver and the user-space API.

Some ideas are in my mind to extend the information query, but I've been busy for other tasks, it's been postponed.

thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#10 lore raw
In reply to [email protected]
Quoted 19 lines · On Tue, Oct 13, 2009 at 3:40 AM, <[email protected]> wrote:
Quoted 9 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

What is the problem, specifically?

With the latest patch I do get the optical output lighting

up and the

Quoted 1 line
Quoted 1 line

receiver detects a PCM signal, but it seems to be just

silence coming

Quoted 3 lines
Quoted 2 lines

through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

Quoted 9 lines
Quoted 2 lines

You can fiddle with hda-verb to issue digital-converter verbs. Possibly you need to flip the digital-enable bit to send

the values...

Well, I think I tried all combinations of the flags on the digital converter in hda_analyzer without any luck. I'm assuming it's something else (presumably codec-specific) that hda_analyzer doesn't know about..

Quoted 3 lines

Hi, Robert
 We cannot duplicate bug of SPDIF Out cannot work on VT1828S board. You said it's fine in Windows, right?

Ahh, I see the problem. I think it's related to what we were talking about with the second SPDIF output: If I play back on subdevice 1 I don't get any output. But if I force playing on substream 1 instead of the default 0 (i.e. hw:0,1,1) then I get audio. I'm assuming that substream 0 is the codec's HDMI output (which actually doesn't exist on this motherboard).

It appears whether or not the "iec958" alias that PulseAudio uses when selecting "Output Digital Stereo" profile actually ends up using substream 1 instead of 0 is based on luck. as it sometimes works and sometimes doesn't. Having different substreams go different places is pretty non-intuitive and it seems software doesn't expect this behavior. I think that the SPDIF and HDMI outputs really should be separate subdevices (i.e. hw:0,1 and hw:0,2 or something) instead, unless something makes this impossible. If the aliases for iec958 and hdmi were set up to point to the correct subdevice then everything would work as it should..

#11 lore raw

At Tue, 13 Oct 2009 21:52:02 -0600,

Quoted 32 lines · Robert Hancock
Quoted 19 lines · On Tue, Oct 13, 2009 at 3:40 AM, <[email protected]> wrote:
Quoted 9 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

What is the problem, specifically?

With the latest patch I do get the optical output lighting

up and the

Quoted 1 line
Quoted 1 line

receiver detects a PCM signal, but it seems to be just

silence coming

Quoted 3 lines
Quoted 2 lines

through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

Quoted 9 lines
Quoted 2 lines

You can fiddle with hda-verb to issue digital-converter verbs. Possibly you need to flip the digital-enable bit to send

the values...

Well, I think I tried all combinations of the flags on the digital converter in hda_analyzer without any luck. I'm assuming it's something else (presumably codec-specific) that hda_analyzer doesn't know about..

Quoted 3 lines

Hi, Robert
 We cannot duplicate bug of SPDIF Out cannot work on VT1828S board. You said it's fine in Windows, right?

Ahh, I see the problem. I think it's related to what we were talking about with the second SPDIF output: If I play back on subdevice 1 I don't get any output. But if I force playing on substream 1 instead of the default 0 (i.e. hw:0,1,1) then I get audio. I'm assuming that substream 0 is the codec's HDMI output (which actually doesn't exist on this motherboard).

Quoted 10 lines

It appears whether or not the "iec958" alias that PulseAudio uses when selecting "Output Digital Stereo" profile actually ends up using substream 1 instead of 0 is based on luck. as it sometimes works and sometimes doesn't. Having different substreams go different places is pretty non-intuitive and it seems software doesn't expect this behavior. I think that the SPDIF and HDMI outputs really should be separate subdevices (i.e. hw:0,1 and hw:0,2 or something) instead, unless something makes this impossible. If the aliases for iec958 and hdmi were set up to point to the correct subdevice then everything would work as it should..

Yes, it's possible to assign two different devices if the pin-config of each digital output is set up properly for SPDIF and HDMI. It won't be too difficult to fix, but I have little time now.

BTW, I'll be off from tomorrow for a while (two weeks) to attend conferences in Tokyo and a few days battery-charging there. So replies will be delayed.

thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#12 lore raw
Quoted 45 lines · Takashi Iwai

At Tue, 13 Oct 2009 21:52:02 -0600,

Quoted 32 lines · Robert Hancock
Quoted 19 lines · On Tue, Oct 13, 2009 at 3:40 AM,  <[email protected]> wrote:
Quoted 9 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

What is the problem, specifically?

With the latest patch I do get the optical output lighting

up and the

Quoted 1 line
Quoted 1 line

receiver detects a PCM signal, but it seems to be just

silence coming

Quoted 3 lines
Quoted 2 lines

through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

Quoted 9 lines
Quoted 2 lines

You can fiddle with hda-verb to issue digital-converter verbs. Possibly you need to flip the digital-enable bit to send

the values...

Well, I think I tried all combinations of the flags on the digital converter in hda_analyzer without any luck. I'm assuming it's something else (presumably codec-specific) that hda_analyzer doesn't know about..

Quoted 3 lines

Hi, Robert
 We cannot duplicate bug of SPDIF Out cannot work on VT1828S board. You said it's fine in Windows, right?

Ahh, I see the problem. I think it's related to what we were talking about with the second SPDIF output: If I play back on subdevice 1 I don't get any output. But if I force playing on substream 1 instead of the default 0 (i.e. hw:0,1,1) then I get audio. I'm assuming that substream 0 is the codec's HDMI output (which actually doesn't exist on this motherboard).

Quoted 10 lines

It appears whether or not the "iec958" alias that PulseAudio uses when selecting "Output Digital Stereo" profile actually ends up using substream 1 instead of 0 is based on luck. as it sometimes works and sometimes doesn't. Having different substreams go different places is pretty non-intuitive and it seems software doesn't expect this behavior. I think that the SPDIF and HDMI outputs really should be separate subdevices (i.e. hw:0,1 and hw:0,2 or something) instead, unless something makes this impossible. If the aliases for iec958 and hdmi were set up to point to the correct subdevice then everything would work as it should..

Quoted 3 lines

Yes, it's possible to assign two different devices if the pin-config of each digital output is set up properly for SPDIF and HDMI. It won't be too difficult to fix, but I have little time now.

Actually, I just checked the version of patch_via.c that's in the sound git tree and it doesn't seem to have this problem with SPDIF output. (I believe the version I was using had one of the second-SPDIF patches that was dropped.) There are still 2 substreams it appears, but both seem to output to SPDIF..

#13 lore raw
Quoted 50 lines · Robert Hancock
Quoted 45 lines · Takashi Iwai

At Tue, 13 Oct 2009 21:52:02 -0600,

Quoted 32 lines · Robert Hancock
Quoted 19 lines · On Tue, Oct 13, 2009 at 3:40 AM,  <[email protected]> wrote:
Quoted 9 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

What is the problem, specifically?

With the latest patch I do get the optical output lighting

up and the

Quoted 1 line
Quoted 1 line

receiver detects a PCM signal, but it seems to be just

silence coming

Quoted 3 lines
Quoted 2 lines

through. (In previous iterations the SPDIF digital converter wasn't being enabled automatically so it didn't get even that far.)

Quoted 9 lines
Quoted 2 lines

You can fiddle with hda-verb to issue digital-converter verbs. Possibly you need to flip the digital-enable bit to send

the values...

Well, I think I tried all combinations of the flags on the digital converter in hda_analyzer without any luck. I'm assuming it's something else (presumably codec-specific) that hda_analyzer doesn't know about..

Quoted 3 lines

Hi, Robert
 We cannot duplicate bug of SPDIF Out cannot work on VT1828S board. You said it's fine in Windows, right?

Ahh, I see the problem. I think it's related to what we were talking about with the second SPDIF output: If I play back on subdevice 1 I don't get any output. But if I force playing on substream 1 instead of the default 0 (i.e. hw:0,1,1) then I get audio. I'm assuming that substream 0 is the codec's HDMI output (which actually doesn't exist on this motherboard).

Quoted 10 lines

It appears whether or not the "iec958" alias that PulseAudio uses when selecting "Output Digital Stereo" profile actually ends up using substream 1 instead of 0 is based on luck. as it sometimes works and sometimes doesn't. Having different substreams go different places is pretty non-intuitive and it seems software doesn't expect this behavior. I think that the SPDIF and HDMI outputs really should be separate subdevices (i.e. hw:0,1 and hw:0,2 or something) instead, unless something makes this impossible. If the aliases for iec958 and hdmi were set up to point to the correct subdevice then everything would work as it should..

Quoted 3 lines

Yes, it's possible to assign two different devices if the pin-config of each digital output is set up properly for SPDIF and HDMI. It won't be too difficult to fix, but I have little time now.

Quoted 5 lines

Actually, I just checked the version of patch_via.c that's in the sound git tree and it doesn't seem to have this problem with SPDIF output. (I believe the version I was using had one of the second-SPDIF patches that was dropped.) There are still 2 substreams it appears, but both seem to output to SPDIF..

Another followup: I've seen the following in dmesg:

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling
MSI: last cmd=0x024f0c00
ALSA sound/pci/hda/hda_intel.c:698: azx_get_response timeout, switching to polling mode: last cmd=0x024f0c00

Any way to tell what was going on here?