Skip to contentSkip to conversation

2 speakers are assigned to the same DAC, this can't support 4.0/2.1 channles

PATCH hwang4 4 participants 28 messages Jun 9, 2015 – Jun 14, 2015 Sound

lore
Share & tools
lore

hwang4

author
#0 lore raw

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are assigned 1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers respectively. But on that HP machine, the speaker has multiple connections for dac, the map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at http://pastebin.ubuntu.com/11667947/
The alsa-info.txt for that Dell machine is at http://pastebin.ubuntu.com/11667982/

To fix this problem, I can use the quirk in the driver to make the speaker have only one connection for dac or do some change in the hda_generic.c like below, in your opinion, which one is better or probably you have a different idea to fix this problem?

sound/pci/hda/hda_generic.c +0 -0
index ac0db16..8194ff1 100644
@@ -1363,6 +1363,7 @@ static int try_assign_dacs(struct hda_codec *codec, int num_outs,
                                dac = try_dac(codec, 
get_primary_out(codec, i), pin);
                        if (!dac)
                                dac = try_dac(codec, dacs[0], pin);
                        if (!dac)
                                dac = try_dac(codec, 
get_primary_out(codec, i), pin);
                        if (dac) {
@@ -1762,6 +1763,12 @@ static int fill_and_eval_dacs(struct hda_codec *codec,
                if (err < 0)
                        return err;
                badness += err;

+ /* if there are 2 speakers and both of them are assigned to the same dac,
+ we need to increase the badness for this situation, because in this situation
+ the 2 speakers can't work together to support 4.0/2.1 channels */
+ if (cfg->speaker_outs == 2 && err < spec->extra_out_badness->no_dac &&
+ spec->multiout.extra_out_nid[1] == 0)

+                       badness += spec->extra_out_badness->no_dac;
        }
        if (!spec->no_multi_io &&
            cfg->line_outs == 1 && cfg->line_out_type != 

AUTO_PIN_SPEAKER_OUT) {

sound/pci/hda/patch_sigmatel.c +2 -0
index bdcda6a..717259c 100644
@@ -2764,6 +2764,8 @@ static const struct snd_pci_quirk stac92hd83xxx_fixup_tbl[] = {
                          "HP bNB13", STAC_HP_BNB13_EQ),
        SND_PCI_QUIRK(PCI_VENDOR_ID_HP, 0x190e,
                          "HP ENVY TS", STAC_HP_ENVY_TS_BASS),
+       SND_PCI_QUIRK(PCI_VENDOR_ID_HP, 0x1967,
+                         "HP ENVY TS", STAC_HP_ENVY_TS_BASS),
        SND_PCI_QUIRK(PCI_VENDOR_ID_HP, 0x1940,
                          "HP bNB13", STAC_HP_BNB13_EQ),
        SND_PCI_QUIRK(PCI_VENDOR_ID_HP, 0x1941,
#1 lore raw

2015-6-9 下午5:39 於 "hwang4" <[email protected]> 寫道:

Quoted 11 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

Quoted 2 lines

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are

assigned

Quoted 6 lines

1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers

respectively.

Quoted 5 lines

But on that HP machine, the speaker has multiple connections for dac, the map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass filter for the subwoofer at the mono pin

2.2. Mono Output
The Mono Out port source selection, power state, and mute characteristics are all independently
controlled by the mono output port controls. EQ does not apply to this path. An internal 2nd order band-pass filter is provided to restrict the output frequencies when using mono out to drive an exter-
nal amplified sub-woofer

Quoted 1 line

The alsa-info.txt for that Dell machine is at

http://pastebin.ubuntu.com/11667982/

The subwoofer is also at mono pin complex, are there any low pass filter for the subwoofer or vendor coeff need to be set ?

Quoted 2 lines

To fix this problem, I can use the quirk in the driver to make the

speaker have

Quoted 1 line

only one connection for dac or do some change in the hda_generic.c like

below, in

Quoted 1 line

your opinion, which one is better or probably you have a different idea

to fix this problem?

Quoted 1 line

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

author
#2 lore raw
Quoted 25 lines · Raymond Yau

2015-6-9 下午5:39 於 "hwang4" <[email protected]> 寫道:

Quoted 10 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

Quoted 2 lines

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are

assigned

Quoted 6 lines

1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers

respectively.

Quoted 4 lines

But on that HP machine, the speaker has multiple connections for dac, the map_single() can't work for this machine.

Quoted 5 lines
Quoted 1 line

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass filter for the subwoofer at the mono pin

Yes, you are right.

Quoted 8 lines

2.2. Mono Output
The Mono Out port source selection, power state, and mute characteristics are all independently
controlled by the mono output port controls. EQ does not apply to this path. An internal 2nd order band-pass filter is provided to restrict the output frequencies when using mono out to drive an exter-
nal amplified sub-woofer

Where did you find this text? Does it mean there is a hardware low frequency pass filter inside the codec?

Quoted 6 lines
Quoted 2 lines

The alsa-info.txt for that Dell machine is at

http://pastebin.ubuntu.com/11667982/

The subwoofer is also at mono pin complex, are there any low pass filter for the subwoofer or vendor coeff need to be set ?

I don't know it, I guess there is no hardware filter, it will work with the software low pass filter in the pulseaudio.

Quoted 11 lines
Quoted 2 lines

To fix this problem, I can use the quirk in the driver to make the

speaker have

Quoted 1 line

only one connection for dac or do some change in the hda_generic.c like

below, in

Quoted 1 line

your opinion, which one is better or probably you have a different idea

to fix this problem?
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

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

#3 lore raw
Quoted 19 lines
Quoted 19 lines
Quoted 11 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

Quoted 2 lines

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are

assigned

Quoted 4 lines

1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers

respectively.

Quoted 2 lines

But on that HP machine, the speaker has multiple connections for dac,

the

Quoted 21 lines
Quoted 9 lines
Quoted 4 lines

map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass filter for the subwoofer at the mono pin

Yes, you are right.

Quoted 8 lines

2.2. Mono Output
The Mono Out port source selection, power state, and mute characteristics are all independently
controlled by the mono output port controls. EQ does not apply to this path. An internal 2nd order band-pass filter is provided to restrict the output frequencies when using mono out to drive an exter-
nal amplified sub-woofer

Quoted 1 line

Where did you find this text? Does it mean there is a hardware low

frequency pass filter inside the codec?

http://www.temposemi.com/products/pclaptop-hd/92hd91/

2.3. Mono output Band-Pass Filter
For many applications, the primary speakers are incapable of reproducing low frequency audio. Therefore it is desirable to implement a woofer or sub-woofer speaker. The mono output is ideal for this task. However, the frequency response should be restricted to prevent interference with the primary speakers. Typically an external filter, known as a cross-over filter, is used. The mono processing path includes a band-pass filter with programmable high and low cut-off frequencies to eliminate the need for an external filter.

2.3.1. Mixer Filter Description The band-pass filter is derived from the common biquadratic filter and provides a 12dB/octave roll-off. The filter may be programmed for a -3dB lower band edge of: 63Hz, 80Hz, 100Hz, 120Hz, 150Hz, 200Hz, 315Hz, or 400Hz.

The filter may be programmed for a -3dB upper band edge of: 150Hz, 200Hz, 250Hz, 315Hz, 400Hz, 500Hz, 630Hz, or 800Hz.

The band-pass filter is enabled by default with a cut-off frequencies at 120Hz and 250Hz. The filter may be bypassed using the associated verb (processing state verb

author
#4 lore raw
Quoted 59 lines · Raymond Yau
Quoted 13 lines
Quoted 13 lines
Quoted 10 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

Quoted 2 lines

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are

assigned

Quoted 8 lines
Quoted 8 lines
Quoted 6 lines

1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers

respectively.

Quoted 1 line

But on that HP machine, the speaker has multiple connections for dac,

the

Quoted 10 lines
Quoted 8 lines
Quoted 4 lines

map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass filter for the subwoofer at the mono pin

Yes, you are right.

Quoted 8 lines
Quoted 7 lines

2.2. Mono Output
The Mono Out port source selection, power state, and mute characteristics are all independently
controlled by the mono output port controls. EQ does not apply to this path. An internal 2nd order band-pass filter is provided to restrict the output frequencies when using mono out to drive an exter-
nal amplified sub-woofer

Where did you find this text? Does it mean there is a hardware low

frequency pass filter inside the codec?

http://www.temposemi.com/products/pclaptop-hd/92hd91/

2.3. Mono output Band-Pass Filter
For many applications, the primary speakers are incapable of reproducing low frequency audio. Therefore it is desirable to implement a woofer or sub-woofer speaker. The mono output is ideal for this task. However, the frequency response should be restricted to prevent interference with the primary speakers. Typically an external filter, known as a cross-over filter, is used. The mono processing path includes a band-pass filter with programmable high and low cut-off frequencies to eliminate the need for an external filter.

2.3.1. Mixer Filter Description The band-pass filter is derived from the common biquadratic filter and provides a 12dB/octave roll-off. The filter may be programmed for a -3dB lower band edge of: 63Hz, 80Hz, 100Hz, 120Hz, 150Hz, 200Hz, 315Hz, or 400Hz.

Quoted 6 lines

The filter may be programmed for a -3dB upper band edge of: 150Hz, 200Hz, 250Hz, 315Hz, 400Hz, 500Hz, 630Hz, or 800Hz.

The band-pass filter is enabled by default with a cut-off frequencies at 120Hz and 250Hz. The filter may be bypassed using the associated verb (processing state verb

Thanks very much, very useful information.

Quoted 6 lines

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

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

#5 lore raw
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

assigned

Quoted 6 lines

1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it,

the

Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 1 line

map_single() can successfully assign the each dac to the 2 speakers

respectively.

Quoted 2 lines

But on that HP machine, the speaker has multiple connections for dac,

the

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines

map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass

filter

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 1 line

for the subwoofer at the mono pin

Yes, you are right.

Quoted 2 lines

2.2. Mono Output
The Mono Out port source selection, power state, and mute

characteristics

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

are all independently
controlled by the mono output port controls. EQ does not apply to this path. An internal 2nd order band-pass filter is provided to restrict

the

Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines

output frequencies when using mono out to drive an exter- nal amplified sub-woofer

Where did you find this text? Does it mean there is a hardware low

frequency pass filter inside the codec?

http://www.temposemi.com/products/pclaptop-hd/92hd91/

Quoted 7 lines
Quoted 7 lines

2.3. Mono output Band-Pass Filter
For many applications, the primary speakers are incapable of reproducing low frequency audio. Therefore it is desirable to implement a woofer or sub-woofer speaker. The mono output is ideal for this task. However, the frequency response should be restricted to prevent interference with the primary speakers. Typically an external filter, known as a cross-over filter, is used. The mono processing path includes a band-pass filter

with

Quoted 1 line
Quoted 1 line

programmable high and low cut-off frequencies to eliminate the need for

an

Quoted 5 lines
Quoted 5 lines

external filter.

2.3.1. Mixer Filter Description The band-pass filter is derived from the common biquadratic filter and provides a 12dB/octave roll-off. The filter may be programmed for a -3dB lower band edge of: 63Hz, 80Hz, 100Hz,

120Hz,

Quoted 12 lines
Quoted 8 lines

150Hz, 200Hz, 315Hz, or 400Hz.

The filter may be programmed for a -3dB upper band edge of: 150Hz, 200Hz, 250Hz, 315Hz, 400Hz, 500Hz, 630Hz, or 800Hz.

The band-pass filter is enabled by default with a cut-off frequencies at 120Hz and 250Hz. The filter may be bypassed using the associated verb (processing state verb

Thanks very much, very useful information.

Do your codec revision support this mono out volume ?

7.4.31.AFG (NID = 01h): DAC3OutAmp (Mono Out Volume)

How do you assign the two volume control to headphone, speaker and subwoofet ?

author
#6 lore raw
Quoted 72 lines · Raymond Yau
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 2 lines

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are

assigned

Quoted 5 lines

1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it,

the

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

map_single() can successfully assign the each dac to the 2 speakers

respectively.

Quoted 1 line

But on that HP machine, the speaker has multiple connections for dac,

the

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines

map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass

filter

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

for the subwoofer at the mono pin

Yes, you are right.

Quoted 2 lines

2.2. Mono Output
The Mono Out port source selection, power state, and mute

characteristics

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

are all independently
controlled by the mono output port controls. EQ does not apply to this path. An internal 2nd order band-pass filter is provided to restrict

the

Quoted 7 lines
Quoted 7 lines
Quoted 3 lines
Quoted 2 lines

output frequencies when using mono out to drive an exter- nal amplified sub-woofer

Where did you find this text? Does it mean there is a hardware low

frequency pass filter inside the codec?

http://www.temposemi.com/products/pclaptop-hd/92hd91/

Quoted 7 lines
Quoted 7 lines

2.3. Mono output Band-Pass Filter
For many applications, the primary speakers are incapable of reproducing low frequency audio. Therefore it is desirable to implement a woofer or sub-woofer speaker. The mono output is ideal for this task. However, the frequency response should be restricted to prevent interference with the primary speakers. Typically an external filter, known as a cross-over filter, is used. The mono processing path includes a band-pass filter

with

Quoted 1 line
Quoted 1 line

programmable high and low cut-off frequencies to eliminate the need for

an

Quoted 5 lines
Quoted 5 lines

external filter.

2.3.1. Mixer Filter Description The band-pass filter is derived from the common biquadratic filter and provides a 12dB/octave roll-off. The filter may be programmed for a -3dB lower band edge of: 63Hz, 80Hz, 100Hz,

120Hz,

Quoted 8 lines
Quoted 8 lines

150Hz, 200Hz, 315Hz, or 400Hz.

The filter may be programmed for a -3dB upper band edge of: 150Hz, 200Hz, 250Hz, 315Hz, 400Hz, 500Hz, 630Hz, or 800Hz.

The band-pass filter is enabled by default with a cut-off frequencies at 120Hz and 250Hz. The filter may be bypassed using the associated verb (processing state verb

Quoted 6 lines
Quoted 3 lines

Thanks very much, very useful information.

Do your codec revision support this mono out volume ?

7.4.31.AFG (NID = 01h): DAC3OutAmp (Mono Out Volume)

I looks like the current driver does not use this to control the volume.

Quoted 3 lines

How do you assign the two volume control to headphone, speaker and subwoofet ?

speaker and headphone are assigned to DAC0 (nid: 0x13), they use the DAC amplifier to control the volume.

subwoofer speaker is assigned to DAC1 (nid: 0x14), it use the DAC amplifier to contorl the volume.

Quoted 5 lines

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

#7 lore raw
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

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

On another Dell machine with realtek codec, there are also 2

speakers,

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

1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone

are

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

assigned

Quoted 6 lines

1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it,

Quoted 7 lines
Quoted 7 lines

the

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 2 lines

map_single() can successfully assign the each dac to the 2 speakers

respectively.

Quoted 2 lines

But on that HP machine, the speaker has multiple connections for

dac,

Quoted 18 lines
Quoted 18 lines
Quoted 11 lines
Quoted 11 lines

the

Quoted 9 lines
Quoted 9 lines
Quoted 5 lines

map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass

filter

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines

for the subwoofer at the mono pin

Yes, you are right.

Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

2.2. Mono Output
The Mono Out port source selection, power state, and mute

characteristics

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

are all independently
controlled by the mono output port controls. EQ does not apply to

this

Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

path. An internal 2nd order band-pass filter is provided to restrict

the

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines

output frequencies when using mono out to drive an exter- nal amplified sub-woofer

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 1 line

Where did you find this text? Does it mean there is a hardware low

frequency pass filter inside the codec?

http://www.temposemi.com/products/pclaptop-hd/92hd91/

2.3. Mono output Band-Pass Filter
For many applications, the primary speakers are incapable of

reproducing

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

low frequency audio. Therefore it is desirable to implement a woofer or sub-woofer speaker. The mono output is ideal for this task. However,

the

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

frequency response should be restricted to prevent interference with

the

Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines

primary speakers. Typically an external filter, known as a cross-over filter, is used. The mono processing path includes a band-pass filter

with

Quoted 1 line
Quoted 1 line
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line

programmable high and low cut-off frequencies to eliminate the need for

an

Quoted 4 lines
Quoted 4 lines

external filter.

2.3.1. Mixer Filter Description The band-pass filter is derived from

the

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

common biquadratic filter and provides a 12dB/octave roll-off. The

filter

Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line

may be programmed for a -3dB lower band edge of: 63Hz, 80Hz, 100Hz,

120Hz,

Quoted 4 lines
Quoted 4 lines

150Hz, 200Hz, 315Hz, or 400Hz.

The filter may be programmed for a -3dB upper band edge of: 150Hz,

200Hz,

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

250Hz, 315Hz, 400Hz, 500Hz, 630Hz, or 800Hz.

The band-pass filter is enabled by default with a cut-off frequencies

at

Quoted 10 lines
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines

120Hz and 250Hz. The filter may be bypassed using the associated verb (processing state verb

Thanks very much, very useful information.

Do your codec revision support this mono out volume ?

7.4.31.AFG (NID = 01h): DAC3OutAmp (Mono Out Volume)

Quoted 7 lines

I looks like the current driver does not use this to control the volume.

Quoted 3 lines

How do you assign the two volume control to headphone, speaker and subwoofet ?

speaker and headphone are assigned to DAC0 (nid: 0x13), they use the DAC

amplifier to control the volume.

Quoted 2 lines

subwoofer speaker is assigned to DAC1 (nid: 0x14), it use the DAC

amplifier to contorl the volume.

Quoted 1 line

Do pulseaudio like this config since there is no mute switch at pin complex of idt codecs and no headphone playback volume/switch?

After applied your patch

Front playback volume/switch are shared by headphone and speaker Base speaker playback volume/switch

But the other 4 channels hda codecs vt1802 have speaker playback switch and subwoofer playback switch

http://git.kernel.org/cgit/linux/kernel/git/tiwai/hda-emu.git/tree/codecs/vt1802-asus-g75

author
#8 lore raw
Quoted 100 lines · Raymond Yau
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2

speakers,

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

1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone

are

Quoted 10 lines
Quoted 10 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

assigned

Quoted 5 lines

1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it,

the

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

map_single() can successfully assign the each dac to the 2 speakers

respectively.

Quoted 1 line

But on that HP machine, the speaker has multiple connections for

dac,

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines
Quoted 8 lines

the

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines

map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass

filter

Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 1 line

for the subwoofer at the mono pin

Yes, you are right.

Quoted 2 lines

2.2. Mono Output
The Mono Out port source selection, power state, and mute

characteristics

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

are all independently
controlled by the mono output port controls. EQ does not apply to

this

Quoted 11 lines
Quoted 11 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

path. An internal 2nd order band-pass filter is provided to restrict

the

Quoted 9 lines
Quoted 9 lines
Quoted 3 lines
Quoted 2 lines

output frequencies when using mono out to drive an exter- nal amplified sub-woofer

Where did you find this text? Does it mean there is a hardware low

frequency pass filter inside the codec?

http://www.temposemi.com/products/pclaptop-hd/92hd91/

2.3. Mono output Band-Pass Filter
For many applications, the primary speakers are incapable of

reproducing

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

low frequency audio. Therefore it is desirable to implement a woofer or sub-woofer speaker. The mono output is ideal for this task. However,

the

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

frequency response should be restricted to prevent interference with

the

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines

primary speakers. Typically an external filter, known as a cross-over filter, is used. The mono processing path includes a band-pass filter

with

Quoted 1 line
Quoted 1 line

programmable high and low cut-off frequencies to eliminate the need for

an

Quoted 3 lines
Quoted 3 lines

external filter.

2.3.1. Mixer Filter Description The band-pass filter is derived from

the

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

common biquadratic filter and provides a 12dB/octave roll-off. The

filter

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

may be programmed for a -3dB lower band edge of: 63Hz, 80Hz, 100Hz,

120Hz,

Quoted 3 lines
Quoted 3 lines

150Hz, 200Hz, 315Hz, or 400Hz.

The filter may be programmed for a -3dB upper band edge of: 150Hz,

200Hz,

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

250Hz, 315Hz, 400Hz, 500Hz, 630Hz, or 800Hz.

The band-pass filter is enabled by default with a cut-off frequencies

at

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines

120Hz and 250Hz. The filter may be bypassed using the associated verb (processing state verb

Thanks very much, very useful information.

Quoted 8 lines
Quoted 3 lines

Do your codec revision support this mono out volume ?

7.4.31.AFG (NID = 01h): DAC3OutAmp (Mono Out Volume)

I looks like the current driver does not use this to control the volume.

Quoted 2 lines

How do you assign the two volume control to headphone, speaker and subwoofet ?

speaker and headphone are assigned to DAC0 (nid: 0x13), they use the DAC

amplifier to control the volume.

Quoted 1 line

subwoofer speaker is assigned to DAC1 (nid: 0x14), it use the DAC

amplifier to contorl the volume.
Do pulseaudio like this config since there is no mute switch at pin complex of idt codecs and no headphone playback volume/switch?

Quoted 7 lines

After applied your patch

Front playback volume/switch are shared by headphone and speaker Base speaker playback volume/switch

But the other 4 channels hda codecs vt1802 have speaker playback switch and subwoofer playback switch

Even without this patch, the base speaker and headphone already shared the same DAC and use single "Front Playback Volume" to control their volume, I did not see any problem from the pulseaudio/desktop so far.

http://pastebin.ubuntu.com/11667982/

About the sharing the switch between headphone and base speaker, this is a new situation, but I did not see obvious problem from pusleaudio/desktop as well.

Quoted 7 lines

http://git.kernel.org/cgit/linux/kernel/git/tiwai/hda-emu.git/tree/codecs/vt1802-asus-g75
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#9 lore raw

2015-6-11 下午4:33 於 "Hui Wang" <[email protected]> 寫道:

Quoted 4 lines · Raymond Yau
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I am trying to enable the subwoofer speaker on a HP laptop, on

this

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

machine, there are two speakers and one headphone, but the BIOS

verb

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

only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I

need

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

to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers

will

Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2

speakers,

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone

are

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

assigned

Quoted 2 lines

1 dac, and the other speaker is assigned another dac, so there is

no

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

problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only

has

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

one connection to dac (hardwired), so when driver assign dac to

it,

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

the

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

map_single() can successfully assign the each dac to the 2

speakers

Quoted 27 lines
Quoted 27 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

respectively.

Quoted 2 lines

But on that HP machine, the speaker has multiple connections for

dac,

Quoted 21 lines
Quoted 21 lines
Quoted 11 lines
Quoted 11 lines

the

Quoted 9 lines
Quoted 9 lines
Quoted 5 lines

map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at

http://pastebin.ubuntu.com/11667947/

Refer to 92HD91, you don't need 4 channel when there is band pass

filter

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 2 lines

for the subwoofer at the mono pin

Yes, you are right.

Quoted 2 lines

2.2. Mono Output
The Mono Out port source selection, power state, and mute

Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines

characteristics

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

are all independently
controlled by the mono output port controls. EQ does not apply to

this

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

path. An internal 2nd order band-pass filter is provided to

restrict

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

the

Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

output frequencies when using mono out to drive an exter- nal amplified sub-woofer

Where did you find this text? Does it mean there is a hardware low

frequency pass filter inside the codec?

Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

http://www.temposemi.com/products/pclaptop-hd/92hd91/

2.3. Mono output Band-Pass Filter
For many applications, the primary speakers are incapable of

reproducing

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

low frequency audio. Therefore it is desirable to implement a woofer

or

Quoted 6 lines
Quoted 6 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

sub-woofer speaker. The mono output is ideal for this task. However,

the

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

frequency response should be restricted to prevent interference with

Quoted 8 lines
Quoted 8 lines

the

Quoted 7 lines
Quoted 7 lines
Quoted 3 lines
Quoted 3 lines

primary speakers. Typically an external filter, known as a cross-over filter, is used. The mono processing path includes a band-pass filter

with

Quoted 2 lines
Quoted 2 lines

programmable high and low cut-off frequencies to eliminate the need

for

Quoted 32 lines
Quoted 32 lines
Quoted 6 lines
Quoted 6 lines

an

Quoted 4 lines
Quoted 4 lines

external filter.

2.3.1. Mixer Filter Description The band-pass filter is derived from

the

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

common biquadratic filter and provides a 12dB/octave roll-off. The

filter

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines

may be programmed for a -3dB lower band edge of: 63Hz, 80Hz, 100Hz,

120Hz,

Quoted 4 lines
Quoted 4 lines

150Hz, 200Hz, 315Hz, or 400Hz.

The filter may be programmed for a -3dB upper band edge of: 150Hz,

200Hz,

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

250Hz, 315Hz, 400Hz, 500Hz, 630Hz, or 800Hz.

The band-pass filter is enabled by default with a cut-off frequencies

at

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines

120Hz and 250Hz. The filter may be bypassed using the associated verb (processing state verb

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

Thanks very much, very useful information.

Do your codec revision support this mono out volume ?

7.4.31.AFG (NID = 01h): DAC3OutAmp (Mono Out Volume)

I looks like the current driver does not use this to control the volume.

You can use hda-verb and use vendor specific get verb with afg node to find out whether you can get back the default values 0x7f

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines

How do you assign the two volume control to headphone, speaker and subwoofet ?

Quoted 8 lines
Quoted 8 lines
Quoted 1 line

speaker and headphone are assigned to DAC0 (nid: 0x13), they use the DAC

amplifier to control the volume.

Quoted 2 lines

subwoofer speaker is assigned to DAC1 (nid: 0x14), it use the DAC

amplifier to contorl the volume.
Do pulseaudio like this config since there is no mute switch at pin

complex

Quoted 11 lines
Quoted 9 lines

of idt codecs and no headphone playback volume/switch?

After applied your patch

Front playback volume/switch are shared by headphone and speaker Base speaker playback volume/switch

But the other 4 channels hda codecs vt1802 have speaker playback switch and subwoofer playback switch

Even without this patch, the base speaker and headphone already shared

the same DAC and use single "Front Playback Volume" to control their volume, I did not see any problem from the pulseaudio/desktop so far.

Quoted 2 lines

http://pastebin.ubuntu.com/11667982/

It won't happen with realtek alc2xx codec since the pin complex of most Realtek codec support mute

Quoted 1 line

About the sharing the switch between headphone and base speaker, this is

a new situation, but I did not see obvious problem from pusleaudio/desktop as well.

Quoted 2 lines
Quoted 2 lines

http://git.kernel.org/cgit/linux/kernel/git/tiwai/hda-emu.git/tree/codecs/vt1802-asus-g75

Quoted 1 line
Quoted 1 line

Independent headphone should be disabled when headphone and internal speaker of notebook share same DAC or only enabled on desktop with codecs support 2+2 , 7.1+2
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#10 lore raw
In reply to Hui Wang
Quoted 10 lines
Quoted 8 lines
Quoted 3 lines

The alsa-info.txt for that Dell machine is at

http://pastebin.ubuntu.com/11667982/

The subwoofer is also at mono pin complex, are there any low pass filter for the subwoofer or vendor coeff need to be set ?

I don't know it, I guess there is no hardware filter, it will work with

the software low pass filter in the pulseaudio.

Quoted 1 line
Quoted 1 line

http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=27&Level=5&Conn=4&ProdID=166

The ALC269 integrates five hardware equalizer bands composed of one low-pass filter, one high-pass filter, and three band-pass filters to compensate for mini-speaker frequency response

Do you mean alc255 does not have tbr hardware equalizer ?

author
#11 lore raw
Quoted 12 lines · Raymond Yau
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines

The alsa-info.txt for that Dell machine is at

http://pastebin.ubuntu.com/11667982/

The subwoofer is also at mono pin complex, are there any low pass

filter

Quoted 3 lines
Quoted 1 line

for the subwoofer or vendor coeff need to be set ?

I don't know it, I guess there is no hardware filter, it will work

Quoted 9 lines

with the software low pass filter in the pulseaudio.

Quoted 1 line
Quoted 1 line

http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=27&Level=5&Conn=4&ProdID=166

The ALC269 integrates five hardware equalizer bands composed of one low-pass filter, one high-pass filter, and three band-pass filters to compensate for mini-speaker frequency response

Do you mean alc255 does not have tbr hardware equalizer ?

I don't have alc255 datasheet, but according to the alc269 feature description, it is highly possible that alc255 also has hardware equalizer.

And do you know how to control those equalizer filters with software or do you know where we can find the detailed document for this part?

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

#12 lore raw
In reply to Hui Wang
Quoted 8 lines
Quoted 6 lines
Quoted 1 line

The alsa-info.txt for that Dell machine is at

http://pastebin.ubuntu.com/11667982/

The subwoofer is also at mono pin complex, are there any low pass filter for the subwoofer or vendor coeff need to be set ?

I don't know it, I guess there is no hardware filter, it will work with

the software low pass filter in the pulseaudio.

Quoted 1 line
Quoted 1 line

The funcional block diagram indicate equaliser is only connected to port D This mean only the internal speaker can use high pass filter

Do you mean your can hear high frequency from the subwoofer of alc255 ?

author
#13 lore raw
Quoted 11 lines · Raymond Yau
Quoted 6 lines
Quoted 5 lines
Quoted 1 line

The alsa-info.txt for that Dell machine is at

http://pastebin.ubuntu.com/11667982/

The subwoofer is also at mono pin complex, are there any low pass filter for the subwoofer or vendor coeff need to be set ?

I don't know it, I guess there is no hardware filter, it will work with

the software low pass filter in the pulseaudio.
The funcional block diagram indicate equaliser is only connected to port D This mean only the internal speaker can use high pass filter

Do you mean your can hear high frequency from the subwoofer of alc255 ?

I am not sure about it, but enable/disable the SW lfe filter will make the sound of subwoofer different

Quoted 6 lines

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

#14 lore raw
In reply to hwang4

At Tue, 09 Jun 2015 17:38:33 +0800,

Quoted 64 lines · hwang4 wrote:

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are assigned
1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers respectively.
But on that HP machine, the speaker has multiple connections for dac, the map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at
http://pastebin.ubuntu.com/11667947/
The alsa-info.txt for that Dell machine is at
http://pastebin.ubuntu.com/11667982/

To fix this problem, I can use the quirk in the driver to make the speaker have
only one connection for dac or do some change in the hda_generic.c like below, in
your opinion, which one is better or probably you have a different idea to fix this problem?

sound/pci/hda/hda_generic.c +0 -0
index ac0db16..8194ff1 100644
@@ -1363,6 +1363,7 @@ static int try_assign_dacs(struct hda_codec 
 *codec, int num_outs,
                                 dac = try_dac(codec, 
 get_primary_out(codec, i), pin);
                         if (!dac)
                                 dac = try_dac(codec, dacs[0], pin);
                         if (!dac)
                                 dac = try_dac(codec, 
get_primary_out(codec, i), pin);
                         if (dac) {
sound/pci/hda/hda_generic.c +2 -0
@@ -1762,6 +1763,12 @@ static int fill_and_eval_dacs(struct hda_codec 
 *codec,
                 if (err < 0)
                         return err;
                 badness += err;
+               /* if there are 2 speakers and both of them are assigned 
 to the same dac,
+                  we need to increase the badness for this situation, 

because in this situation
+ the 2 speakers can't work together to support 4.0/2.1
channels */
+ if (cfg->speaker_outs == 2 && err <
spec->extra_out_badness->no_dac &&

sound/pci/hda/hda_generic.c

Quoted 2 lines
sound/pci/hda/hda_generic.c +2 -0
+                   spec->multiout.extra_out_nid[1] == 0)
+                       badness += spec->extra_out_badness->no_dac;

This doesn't look like the correct place to add badness for the missing surround speaker. This function is called for each path, so it's evaluated not only for speakers.

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested patch is below.

Takashi

---

sound/pci/hda/hda_generic.c +12 -1
index ac0db1679f09..ee03fb884426 100644
@@ -1292,6 +1292,15 @@ const struct badness_table hda_extra_out_badness = {
 };
 EXPORT_SYMBOL_GPL(hda_extra_out_badness);
 
+static const struct badness_table hda_speaker_out_badness = {
+	.no_primary_dac = BAD_NO_DAC,
+	.no_dac = BAD_NO_DAC,
+	.shared_primary = BAD_NO_EXTRA_DAC,
+	.shared_surr = BAD_NO_EXTRA_DAC,
+	.shared_clfe = BAD_SHARED_EXTRA_SURROUND,
+	.shared_surr_main = BAD_NO_EXTRA_SURR_DAC,
+};
+
 /* get the DAC of the primary output corresponding to the given array index */
 static hda_nid_t get_primary_out(struct hda_codec *codec, int idx)
 {
@@ -1758,7 +1767,7 @@ static int fill_and_eval_dacs(struct hda_codec *codec,
 				      cfg->speaker_pins,
 				      spec->multiout.extra_out_nid,
 				      spec->speaker_paths,
-				      spec->extra_out_badness);
+				      spec->speaker_out_badness);
 		if (err < 0)
 			return err;
 		badness += err;
@@ -4789,6 +4798,8 @@ int snd_hda_gen_parse_auto_config(struct hda_codec *codec,
 		spec->main_out_badness = &hda_main_out_badness;
 	if (!spec->extra_out_badness)
 		spec->extra_out_badness = &hda_extra_out_badness;
+	if (!spec->speaker_out_badness)
+		spec->speaker_out_badness = &hda_speaker_out_badness;
 
 	fill_all_dac_nids(codec);
 
sound/pci/hda/hda_generic.h +1 -0
index 56e4139b9032..1f868de1aec4 100644
@@ -246,6 +246,7 @@ struct hda_gen_spec {
 	/* badness tables for output path evaluations */
 	const struct badness_table *main_out_badness;
 	const struct badness_table *extra_out_badness;
+	const struct badness_table *speaker_out_badness;
 
 	/* preferred pin/DAC pairs; an array of paired NIDs */
 	const hda_nid_t *preferred_dacs;
sound/pci/hda/patch_via.c +1 -0
index 0521be8d46a8..9e9d0456dab7 100644
@@ -579,6 +579,7 @@ static int via_parse_auto_config(struct hda_codec *codec)
 
 	spec->gen.main_out_badness = &via_main_out_badness;
 	spec->gen.extra_out_badness = &via_extra_out_badness;
+	spec->gen.speaker_out_badness = &via_extra_out_badness;
 
 	err = snd_hda_parse_pin_defcfg(codec, &spec->gen.autocfg, NULL, 0);
 	if (err < 0)
author
#15 lore raw
Quoted 71 lines · Takashi Iwai

At Tue, 09 Jun 2015 17:38:33 +0800,

Quoted 63 lines · hwang4 wrote:

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are assigned
1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers respectively.
But on that HP machine, the speaker has multiple connections for dac, the map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at
http://pastebin.ubuntu.com/11667947/
The alsa-info.txt for that Dell machine is at
http://pastebin.ubuntu.com/11667982/

To fix this problem, I can use the quirk in the driver to make the speaker have
only one connection for dac or do some change in the hda_generic.c like below, in
your opinion, which one is better or probably you have a different idea to fix this problem?

sound/pci/hda/hda_generic.c +0 -0
index ac0db16..8194ff1 100644
@@ -1363,6 +1363,7 @@ static int try_assign_dacs(struct hda_codec
 *codec, int num_outs,
                                  dac = try_dac(codec,
 get_primary_out(codec, i), pin);
                          if (!dac)
                                  dac = try_dac(codec, dacs[0], pin);
                          if (!dac)
                                  dac = try_dac(codec,
get_primary_out(codec, i), pin);
                          if (dac) {
sound/pci/hda/hda_generic.c +2 -0
@@ -1762,6 +1763,12 @@ static int fill_and_eval_dacs(struct hda_codec
 *codec,
                  if (err < 0)
                          return err;
                  badness += err;
+               /* if there are 2 speakers and both of them are assigned
 to the same dac,
+                  we need to increase the badness for this situation,

because in this situation
+ the 2 speakers can't work together to support 4.0/2.1
channels */
+ if (cfg->speaker_outs == 2 && err <
spec->extra_out_badness->no_dac &&

sound/pci/hda/hda_generic.c

Quoted 2 lines
sound/pci/hda/hda_generic.c +2 -0
+                   spec->multiout.extra_out_nid[1] == 0)
+                       badness += spec->extra_out_badness->no_dac;

This doesn't look like the correct place to add badness for the missing surround speaker. This function is called for each path, so it's evaluated not only for speakers.

Quoted 3 lines

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested patch is below.

Got it, I will test it soon. Thanks.

Quoted 71 lines

Takashi

---

sound/pci/hda/hda_generic.c +12 -1
index ac0db1679f09..ee03fb884426 100644
@@ -1292,6 +1292,15 @@ const struct badness_table hda_extra_out_badness = {
  };
  EXPORT_SYMBOL_GPL(hda_extra_out_badness);
 
+static const struct badness_table hda_speaker_out_badness = {
+	.no_primary_dac = BAD_NO_DAC,
+	.no_dac = BAD_NO_DAC,
+	.shared_primary = BAD_NO_EXTRA_DAC,
+	.shared_surr = BAD_NO_EXTRA_DAC,
+	.shared_clfe = BAD_SHARED_EXTRA_SURROUND,
+	.shared_surr_main = BAD_NO_EXTRA_SURR_DAC,
+};
+
  /* get the DAC of the primary output corresponding to the given array index */
  static hda_nid_t get_primary_out(struct hda_codec *codec, int idx)
  {
@@ -1758,7 +1767,7 @@ static int fill_and_eval_dacs(struct hda_codec *codec,
  				      cfg->speaker_pins,
  				      spec->multiout.extra_out_nid,
  				      spec->speaker_paths,
-				      spec->extra_out_badness);
+				      spec->speaker_out_badness);
  		if (err < 0)
  			return err;
  		badness += err;
@@ -4789,6 +4798,8 @@ int snd_hda_gen_parse_auto_config(struct hda_codec *codec,
  		spec->main_out_badness = &hda_main_out_badness;
  	if (!spec->extra_out_badness)
  		spec->extra_out_badness = &hda_extra_out_badness;
+	if (!spec->speaker_out_badness)
+		spec->speaker_out_badness = &hda_speaker_out_badness;
 
  	fill_all_dac_nids(codec);
 
sound/pci/hda/hda_generic.h +1 -0
index 56e4139b9032..1f868de1aec4 100644
@@ -246,6 +246,7 @@ struct hda_gen_spec {
  	/* badness tables for output path evaluations */
  	const struct badness_table *main_out_badness;
  	const struct badness_table *extra_out_badness;
+	const struct badness_table *speaker_out_badness;
 
  	/* preferred pin/DAC pairs; an array of paired NIDs */
  	const hda_nid_t *preferred_dacs;
sound/pci/hda/patch_via.c +1 -0
index 0521be8d46a8..9e9d0456dab7 100644
@@ -579,6 +579,7 @@ static int via_parse_auto_config(struct hda_codec *codec)
 
  	spec->gen.main_out_badness = &via_main_out_badness;
  	spec->gen.extra_out_badness = &via_extra_out_badness;
+	spec->gen.speaker_out_badness = &via_extra_out_badness;
 
  	err = snd_hda_parse_pin_defcfg(codec, &spec->gen.autocfg, NULL, 0);
  	if (err < 0)

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

author
#16 lore raw
Quoted 74 lines · Hui Wang
Quoted 73 lines · Takashi Iwai

At Tue, 09 Jun 2015 17:38:33 +0800,

Quoted 65 lines · hwang4 wrote:

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are assigned
1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers respectively.
But on that HP machine, the speaker has multiple connections for dac, the map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at
http://pastebin.ubuntu.com/11667947/
The alsa-info.txt for that Dell machine is at
http://pastebin.ubuntu.com/11667982/

To fix this problem, I can use the quirk in the driver to make the speaker have
only one connection for dac or do some change in the hda_generic.c like below, in
your opinion, which one is better or probably you have a different idea to fix this problem?

sound/pci/hda/hda_generic.c +0 -0
index ac0db16..8194ff1 100644
@@ -1363,6 +1363,7 @@ static int try_assign_dacs(struct hda_codec
 *codec, int num_outs,
                                  dac = try_dac(codec,
 get_primary_out(codec, i), pin);
                          if (!dac)
                                  dac = try_dac(codec, dacs[0], pin);
                          if (!dac)
                                  dac = try_dac(codec,
get_primary_out(codec, i), pin);
                          if (dac) {
sound/pci/hda/hda_generic.c +1 -0
@@ -1762,6 +1763,12 @@ static int fill_and_eval_dacs(struct hda_codec
 *codec,
                  if (err < 0)
                          return err;
                  badness += err;
+               /* if there are 2 speakers and both of them are 

assigned
to the same dac,
+ we need to increase the badness for this situation,
because in this situation
+ the 2 speakers can't work together to support
4.0/2.1
channels */
+ if (cfg->speaker_outs == 2 && err <
spec->extra_out_badness->no_dac &&

sound/pci/hda/hda_generic.c

Quoted 2 lines
sound/pci/hda/hda_generic.c +2 -0
+                   spec->multiout.extra_out_nid[1] == 0)
+                       badness += spec->extra_out_badness->no_dac;

This doesn't look like the correct place to add badness for the missing surround speaker. This function is called for each path, so it's evaluated not only for speakers.

Quoted 5 lines
Quoted 3 lines

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested patch is below.

Got it, I will test it soon. Thanks.

Hi Takashi,

Your patch can fix the problem, it works very well.

Thanks,
Hui.

Quoted 63 lines
Quoted 63 lines

Takashi

---

sound/pci/hda/hda_generic.c +8 -0
index ac0db1679f09..ee03fb884426 100644
@@ -1292,6 +1292,15 @@ const struct badness_table 
 hda_extra_out_badness = {
  };
  EXPORT_SYMBOL_GPL(hda_extra_out_badness);
  +static const struct badness_table hda_speaker_out_badness = {
+    .no_primary_dac = BAD_NO_DAC,
+    .no_dac = BAD_NO_DAC,
+    .shared_primary = BAD_NO_EXTRA_DAC,
+    .shared_surr = BAD_NO_EXTRA_DAC,
+    .shared_clfe = BAD_SHARED_EXTRA_SURROUND,
+    .shared_surr_main = BAD_NO_EXTRA_SURR_DAC,
+};
+
  /* get the DAC of the primary output corresponding to the given 

array index */
static hda_nid_t get_primary_out(struct hda_codec *codec, int idx) {

sound/pci/hda/hda_generic.c +1 -1
@@ -1758,7 +1767,7 @@ static int fill_and_eval_dacs(struct hda_codec 
 *codec,
                        cfg->speaker_pins,
                        spec->multiout.extra_out_nid,
                        spec->speaker_paths,
-                      spec->extra_out_badness);
+                      spec->speaker_out_badness);
          if (err < 0)
              return err;
          badness += err;
sound/pci/hda/hda_generic.c +2 -0
@@ -4789,6 +4798,8 @@ int snd_hda_gen_parse_auto_config(struct 
 hda_codec *codec,
          spec->main_out_badness = &hda_main_out_badness;
      if (!spec->extra_out_badness)
          spec->extra_out_badness = &hda_extra_out_badness;
+    if (!spec->speaker_out_badness)
+        spec->speaker_out_badness = &hda_speaker_out_badness;
        fill_all_dac_nids(codec);
  diff --git a/sound/pci/hda/hda_generic.h b/sound/pci/hda/hda_generic.h

index 56e4139b9032..1f868de1aec4 100644

sound/pci/hda/hda_generic.h +1 -0
@@ -246,6 +246,7 @@ struct hda_gen_spec {
      /* badness tables for output path evaluations */
      const struct badness_table *main_out_badness;
      const struct badness_table *extra_out_badness;
+    const struct badness_table *speaker_out_badness;
        /* preferred pin/DAC pairs; an array of paired NIDs */
      const hda_nid_t *preferred_dacs;
sound/pci/hda/patch_via.c +1 -0
index 0521be8d46a8..9e9d0456dab7 100644
@@ -579,6 +579,7 @@ static int via_parse_auto_config(struct hda_codec 
 *codec)
        spec->gen.main_out_badness = &via_main_out_badness;
      spec->gen.extra_out_badness = &via_extra_out_badness;
+    spec->gen.speaker_out_badness = &via_extra_out_badness;
Quoted 9 lines
Quoted 8 lines
sound/pci/hda/patch_via.c +0 -0
        err = snd_hda_parse_pin_defcfg(codec, &spec->gen.autocfg, 
 NULL, 0);
      if (err < 0)

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

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

#17 lore raw

At Wed, 10 Jun 2015 12:19:58 +0800,

Quoted 79 lines · hwang4 wrote:
Quoted 75 lines · Hui Wang
Quoted 74 lines · Takashi Iwai

At Tue, 09 Jun 2015 17:38:33 +0800,

Quoted 66 lines · hwang4 wrote:

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are assigned
1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers respectively.
But on that HP machine, the speaker has multiple connections for dac, the
map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at
http://pastebin.ubuntu.com/11667947/
The alsa-info.txt for that Dell machine is at
http://pastebin.ubuntu.com/11667982/

To fix this problem, I can use the quirk in the driver to make the speaker have
only one connection for dac or do some change in the hda_generic.c like below, in
your opinion, which one is better or probably you have a different idea to fix this problem?

sound/pci/hda/hda_generic.c +0 -0
index ac0db16..8194ff1 100644
@@ -1363,6 +1363,7 @@ static int try_assign_dacs(struct hda_codec
 *codec, int num_outs,
                                  dac = try_dac(codec,
 get_primary_out(codec, i), pin);
                          if (!dac)
                                  dac = try_dac(codec, dacs[0], pin);
                          if (!dac)
                                  dac = try_dac(codec,
get_primary_out(codec, i), pin);
                          if (dac) {
sound/pci/hda/hda_generic.c +1 -0
@@ -1762,6 +1763,12 @@ static int fill_and_eval_dacs(struct hda_codec
 *codec,
                  if (err < 0)
                          return err;
                  badness += err;
+               /* if there are 2 speakers and both of them are 

assigned
to the same dac,
+ we need to increase the badness for this situation,
because in this situation
+ the 2 speakers can't work together to support
4.0/2.1
channels */
+ if (cfg->speaker_outs == 2 && err <
spec->extra_out_badness->no_dac &&

sound/pci/hda/hda_generic.c

Quoted 2 lines
sound/pci/hda/hda_generic.c +2 -0
+                   spec->multiout.extra_out_nid[1] == 0)
+                       badness += spec->extra_out_badness->no_dac;

This doesn't look like the correct place to add badness for the missing surround speaker. This function is called for each path, so it's evaluated not only for speakers.

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested patch is below.

Got it, I will test it soon. Thanks.

Hi Takashi,

Your patch can fix the problem, it works very well.

OK, good to know. I'd like to test a bit more via hda-emu whether this gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

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

#18 lore raw

At Wed, 10 Jun 2015 12:28:39 +0200,

Quoted 6 lines · Takashi Iwai
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested patch is below.

Got it, I will test it soon. Thanks.

Quoted 7 lines
Quoted 3 lines

Hi Takashi,

Your patch can fix the problem, it works very well.

OK, good to know. I'd like to test a bit more via hda-emu whether this gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

This change alone results in regressions on machines that are capable of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has to be increased as well. It's damn sensitive.

But, now I wonder now whether blindly applying this is good. Suppose a machine with 2.1 speaker and one headphone, but the codec has only two DACs. With this setup, now the headphone and the speaker share the same DAC, as the cost of having individual 2.1 speaker volume. Is this more useful than having individual volumes for speaker and headphone?

Maybe the machine you're trying to support has a different situation. So applying the new rule to limited devices is fine. But if so, it's not necessarily to be an adjustment of badness table, but just you can provide the simple DAC/pin preference map explicitly in the fixup.

Takashi

author
#19 lore raw
Quoted 17 lines · Takashi Iwai

At Wed, 10 Jun 2015 12:28:39 +0200,

Quoted 11 lines · Takashi Iwai
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested patch is below.

Got it, I will test it soon. Thanks.

Hi Takashi,

Your patch can fix the problem, it works very well.

OK, good to know. I'd like to test a bit more via hda-emu whether this gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

This change alone results in regressions on machines that are capable of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has to be increased as well. It's damn sensitive.

Quoted 6 lines

But, now I wonder now whether blindly applying this is good. Suppose a machine with 2.1 speaker and one headphone, but the codec has only two DACs. With this setup, now the headphone and the speaker share the same DAC, as the cost of having individual 2.1 speaker volume. Is this more useful than having individual volumes for speaker and headphone?

If having individual volumes for speaker and headphone (the speakers share the same DAC), there will be no "Front Speaker" and "Bass Speaker", as a result, in the userspace, pulseaudio can't regard the 2.1 channels is a valid profile.

Quoted 5 lines

Maybe the machine you're trying to support has a different situation. So applying the new rule to limited devices is fine. But if so, it's not necessarily to be an adjustment of badness table, but just you can provide the simple DAC/pin preference map explicitly in the fixup.

This is a good idea, so far this machine is the only one with this problem, it is suitable to use a machine specific fixup. If in future, we have more machines with this problem, then we will think about a general way to fix it.

Quoted 8 lines

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

#20 lore raw
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested patch

is

Quoted 16 lines
Quoted 16 lines
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines
Quoted 1 line

below.

Got it, I will test it soon. Thanks.

Hi Takashi,

Your patch can fix the problem, it works very well.

OK, good to know. I'd like to test a bit more via hda-emu whether this gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

This change alone results in regressions on machines that are capable of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has to be increased as well. It's damn sensitive.

Quoted 8 lines
Quoted 6 lines

But, now I wonder now whether blindly applying this is good. Suppose a machine with 2.1 speaker and one headphone, but the codec has only two DACs. With this setup, now the headphone and the speaker share the same DAC, as the cost of having individual 2.1 speaker volume. Is this more useful than having individual volumes for speaker and headphone?

If having individual volumes for speaker and headphone (the speakers

share the same DAC), there will be no "Front Speaker" and "Bass Speaker", as a result, in the userspace, pulseaudio can't regard the 2.1 channels is a valid profile.

Quoted 1 line

Do you mean you can still hear high frequency from the subwoofer of 92hd91 (i.e. pulseaudio lfe filtering is much better than the band pass filter in 92hd91)

How much auddional cpu need to enable lfe filtering ?

author
#21 lore raw
Quoted 22 lines · Raymond Yau
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested patch

is

Quoted 19 lines
Quoted 19 lines
Quoted 9 lines
Quoted 6 lines
Quoted 3 lines
Quoted 1 line

below.

Got it, I will test it soon. Thanks.

Hi Takashi,

Your patch can fix the problem, it works very well.

OK, good to know. I'd like to test a bit more via hda-emu whether this gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

This change alone results in regressions on machines that are capable of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has to be increased as well. It's damn sensitive.

But, now I wonder now whether blindly applying this is good. Suppose a machine with 2.1 speaker and one headphone, but the codec has only two DACs. With this setup, now the headphone and the speaker share the same DAC, as the cost of having individual 2.1 speaker volume. Is this more useful than having individual volumes for speaker and headphone?

Quoted 7 lines
Quoted 1 line

If having individual volumes for speaker and headphone (the speakers

share the same DAC), there will be no "Front Speaker" and "Bass Speaker", as a result, in the userspace, pulseaudio can't regard the 2.1 channels is a valid profile.
Do you mean you can still hear high frequency from the subwoofer of 92hd91 (i.e. pulseaudio lfe filtering is much better than the band pass filter in 92hd91)

I don't mean we will definitely enable the lfe filter in the pulseaudio, if the codec has HW filter, we can disable the lfe filter in the pulseaudio. The problem is if we don't choose 2.1 channels, the pulseaudio will not feed the data to the subwoofer speaker, so there is no sound coming from the subwoofer speaker.

2.1 channles != enabling lfe filter.

Quoted 8 lines

How much auddional cpu need to enable lfe filtering ?
_______________________________________________
Alsa-devel mailing list [email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#22 lore raw
In reply to Takashi Iwai
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

A cleaner way would be to prepare a different badness table for the speaker, and increase the value for shared_surr. An untested

patch is

Quoted 15 lines
Quoted 10 lines
Quoted 6 lines
Quoted 3 lines
Quoted 1 line

below.

Got it, I will test it soon. Thanks.

Hi Takashi,

Your patch can fix the problem, it works very well.

OK, good to know. I'd like to test a bit more via hda-emu whether this gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

This change alone results in regressions on machines that are capable of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has to be increased as well. It's damn sensitive.

Quoted 6 lines

But, now I wonder now whether blindly applying this is good. Suppose a machine with 2.1 speaker and one headphone, but the codec has only two DACs. With this setup, now the headphone and the speaker share the same DAC, as the cost of having individual 2.1 speaker volume. Is this more useful than having individual volumes for speaker and headphone?

Some realtek codec e.g. alc262

Supports MONO line output with independent volume control

http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=27&Level=5&Conn=4&ProdID=40

Badness table cannot be applied to all realtek codecs

#23 lore raw
In reply to Takashi Iwai
Quoted 14 lines · Takashi Iwai

At Wed, 10 Jun 2015 12:28:39 +0200,

Quoted 1 line · Takashi Iwai

OK, good to know. I'd like to test a bit more via hda-emu whether this gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

This change alone results in regressions on machines that are capable of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has to be increased as well. It's damn sensitive.

But, now I wonder now whether blindly applying this is good. Suppose a machine with 2.1 speaker and one headphone, but the codec has only two DACs. With this setup, now the headphone and the speaker share the same DAC, as the cost of having individual 2.1 speaker volume. Is this more useful than having individual volumes for speaker and headphone?

Quoted 4 lines

Maybe the machine you're trying to support has a different situation. So applying the new rule to limited devices is fine. But if so, it's not necessarily to be an adjustment of badness table, but just you can provide the simple DAC/pin preference map explicitly in the fixup.

Oh, this is an interesting trade-off.

In the PulseAudio desktop scenario, we automute the speaker, and PulseAudio remembers the individual headphone and speaker volumes. So in this case, there is no benefit from having individual headphone and speaker volume at the ALSA level.

However if a user wants to turn off automute, then there is a need for being able to adjust headphone and speaker volume individually.

But it's not just a question of volume control for 2.1. Being able to send a different stream to the subwoofer could be useful too, especially if the hardware filter is bad or non-existing.

So my gut feeling leans towards using the second DAC for the subwoofer speaker being the more useful default, but it's not a clear cut.

// David

#24 lore raw

OK, good to know. I'd like to test a bit more via hda-emu whether this

Quoted 22 lines
Quoted 14 lines
Quoted 3 lines

gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

This change alone results in regressions on machines that are capable of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has to be increased as well. It's damn sensitive.

But, now I wonder now whether blindly applying this is good. Suppose a machine with 2.1 speaker and one headphone, but the codec has only two DACs. With this setup, now the headphone and the speaker share the same DAC, as the cost of having individual 2.1 speaker volume. Is this more useful than having individual volumes for speaker and headphone?

Quoted 5 lines

Maybe the machine you're trying to support has a different situation. So applying the new rule to limited devices is fine. But if so, it's not necessarily to be an adjustment of badness table, but just you can provide the simple DAC/pin preference map explicitly in the fixup.

Oh, this is an interesting trade-off.

Quoted 8 lines

In the PulseAudio desktop scenario, we automute the speaker, and PulseAudio remembers the individual headphone and speaker volumes. So in this case, there is no benefit from having individual headphone and speaker volume at the ALSA level.

However if a user wants to turn off automute, then there is a need for being able to adjust headphone and speaker volume individually.

Do "front Playback volume" a good name when volume control is shared by headphone and speaker" ?

in desktop with alc66x , volume control shared by headphone and Line Out is name as "Front" because it support 5.1

Quoted 5 lines

But it's not just a question of volume control for 2.1. Being able to send a different stream to the subwoofer could be useful too, especially if the hardware filter is bad or non-existing.

when subwoofer is using stereo pin complex (usually with 6, 8 or 10 channels codec), only one left or right channel is used (e.g. Asus N series note book external sonic master subwoofer use right channel but acer aspire 5930g internal subwoofer using left channel

FL, FR LFE N/A
FL, FR, N/A, LFE

how do pulseaudio perform lfe filter when subwoofer is using mono pin since the downmix widget mix left and right channel and scale down the volume ?

FL, FR, LFE, LFE

do it need more CPU than those use one channel of stereo pin complex

For those 2 channel hda codec 's subwoofer must use mono pin

Quoted 3 lines
#25 lore raw
In reply to David Henningsson

At Fri, 12 Jun 2015 08:07:20 +0200,

Quoted 35 lines · David Henningsson
Quoted 16 lines · Takashi Iwai

At Wed, 10 Jun 2015 12:28:39 +0200,

Quoted 3 lines · Takashi Iwai

OK, good to know. I'd like to test a bit more via hda-emu whether this gives any ill effects. So far, this seems fixing a few other machines, too, so it's a good thing to have in general.

This change alone results in regressions on machines that are capable of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has to be increased as well. It's damn sensitive.

But, now I wonder now whether blindly applying this is good. Suppose a machine with 2.1 speaker and one headphone, but the codec has only two DACs. With this setup, now the headphone and the speaker share the same DAC, as the cost of having individual 2.1 speaker volume. Is this more useful than having individual volumes for speaker and headphone?

Quoted 4 lines

Maybe the machine you're trying to support has a different situation. So applying the new rule to limited devices is fine. But if so, it's not necessarily to be an adjustment of badness table, but just you can provide the simple DAC/pin preference map explicitly in the fixup.

Oh, this is an interesting trade-off.

In the PulseAudio desktop scenario, we automute the speaker, and PulseAudio remembers the individual headphone and speaker volumes. So in this case, there is no benefit from having individual headphone and speaker volume at the ALSA level.

However if a user wants to turn off automute, then there is a need for being able to adjust headphone and speaker volume individually.

Quoted 6 lines

But it's not just a question of volume control for 2.1. Being able to send a different stream to the subwoofer could be useful too, especially if the hardware filter is bad or non-existing.

So my gut feeling leans towards using the second DAC for the subwoofer speaker being the more useful default, but it's not a clear cut.

Right, this is indeed a difficult problem, and probably there is never a clear answer.

Another interesting examples are:
A. 3 DACs, 2 HP, 2 speakers
B. 3 DACs, 2 HP, 1 mic, 1 speaker
C. 4 DACs, 2 HP, 1 mic, 2 speakers

For B and C, user expects the possible 5.1 outputs by retasking the mic. But then you'll lose the individual volume control with the speaker.

Takashi

#26 lore raw
In reply to David Henningsson
Quoted 3 lines

Oh, this is an interesting trade-off.

In the PulseAudio desktop scenario, we automute the speaker, and

PulseAudio remembers the individual headphone and speaker volumes. So in this case, there is no benefit from having individual headphone and speaker volume at the ALSA level.

Quoted 2 lines

However if a user wants to turn off automute, then there is a need for

being able to adjust headphone and speaker volume individually.

Quoted 2 lines

But it's not just a question of volume control for 2.1. Being able to

send a different stream to the subwoofer could be useful too, especially if the hardware filter is bad or non-existing.

Quoted 2 lines

It is not just low pass filter with subwoofer

Pulseaudio seem also perform high pass filter at the same time

http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=f3ebf6b667b155f5fe6526bd70881c79e07d7874

92hd91 have high pass filter for internal speakers

2.20.BTL Amplifier High-Pass Filter

For mobile applications, speakers are often incapable of reproducing low frequency audio and unable to handle the maximum output power of the BTL amplifier. A high-pass filter is implemented in the BTL output path to reduce the amount of low frequency energy reaching speakers attached to the BTL amplifier. This can prevent speaker failure.

2.20.1.Filter Description

The high-pass filter is derived from the common biquadratic filter and provides a 12dB/octave roll-off. The filter may be programmed for a -3dB response at: 100Hz, 200Hz, 300Hz, 400Hz, 500Hz, 750Hz, 1KHz, or 2KHz. The high pass filter is enabled by default with a cut-off frequency of 300Hz. The filter may be bypassed using the associated verb (processing state verb).

#27 lore raw
In reply to Takashi Iwai
Quoted 17 lines
Quoted 17 lines

I am trying to enable the subwoofer speaker on a HP laptop, on this machine, there are two speakers and one headphone, but the BIOS verb only enabled one speaker(nid 0xd) and one headphone(nid 0xb), I need to use quirk in the kernel driver to configure the second speaker (subwoofer speaker, nid 0x10). Under current alsa driver, the headphone will be assigned a dac (nid 0x13) and the 2 speakers will be assigned a dac (nid 0x14), this assignment is not good since 2 speakers share the same dac, this means 2 speakers can't work at the same time to support 4.0/2.1 channels.

On another Dell machine with realtek codec, there are also 2 speakers, 1 headphone and 2 dacs, on this machine, 1 speaker and 1 headphone are assigned
1 dac, and the other speaker is assigned another dac, so there is no problem for this machine to support 4.0/2.1 channels.

Quoted 5 lines
Quoted 5 lines

Through debugging, I found on Dell machine, the speaker nid only has one connection to dac (hardwired), so when driver assign dac to it, the map_single() can successfully assign the each dac to the 2 speakers respectively.
But on that HP machine, the speaker has multiple connections for dac,

the

Quoted 5 lines
Quoted 5 lines

map_single() can't work for this machine.

The alsa-info.txt for that HP machine is at
http://pastebin.ubuntu.com/11667947/

Node 0x13 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L
Control: name="Headphone Playback Volume", index=0, device=0

    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Headphone Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0

Device: name="92HD91BXX Analog", type="Audio", device=0 Amp-Out caps: N/A
Amp-Out vals: [0x80 0x80]
Converter: stream=5, channel=0
Power states:
Power: setting=D0, actual=D0
Delay: 13 samples
Node 0x14 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L
Control: name="Speaker Playback Volume", index=0, device=0

    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Speaker Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0

Amp-Out caps: N/A
Amp-Out vals: [0x64 0x64]
Converter: stream=5, channel=0
Power states:
Power: setting=D0, actual=D0
Delay: 13 samples

Do hda_proc.c or hda_codec use the correct verb to get amp out cap of idt codecs ?

92hd91 datasheet has default values of amp out caps

Why amp out caps are N/A ?

7.14.2.DAC0 (NID = 13h): OutAmpLeft

7.14.3.DAC0 (NID = 13h): OutAmpRight

7.15.2.DAC1 (NID = 14h): OutAmpLeft

7.15.3.DAC1 (NID = 14h): OutAmpRight