- Alsa-devel - mailman.alsa-project.org

Re: [alsa-devel] ASUS V1Sn can have digout
by Takashi Iwai 05 Nov '08

05 Nov '08

At Wed, 5 Nov 2008 15:44:03 +1030, asto wrote: > > > Thanks. Could you give a summary line, a chnage log and your > > sign-off to merge to the upstream? > > See $LINUX/Documentation/SubmittingPatches for details. > > New version of patch attached. > > ASUS V1S should have digital out > > SUMMARY: > Asus V1s series laptops have an ALC660VD with PCI id: 0x1043, 0x1633. > 1.) remove the previous behaviour of mapping that to the ALC861VD_LENOVO device. > 2.) add a new ALC660VD_V1S device based on ALC861VD_LENOVO, with an > added digital out. > Signed-off-by: Tristan Aston <astrotris(a)gmail.com> Thanks, applied now with a slight modification (ALC660VD_V1s -> ALC660VD_ASUS_V1S). BTW, your patch couldn't be applied as is because your MUA seems to break tabs. Please fix MUA setting, or use an attachment if it's difficult. Takashi > > --- alsa-driver/alsa-kernel/pci/hda/patch_realtek.c.orig > 2008-11-05 15:26:41.000000000 +1030 > +++ alsa-driver/alsa-kernel/pci/hda/patch_realtek.c 2008-11-05 > 15:26:58.000000000 +1030 > @@ -153,6 +153,7 @@ enum { > enum { > ALC660VD_3ST, > ALC660VD_3ST_DIG, > + ALC660VD_V1S, > ALC861VD_3ST, > ALC861VD_3ST_DIG, > ALC861VD_6ST_DIG, > @@ -13843,6 +13844,7 @@ static void alc861vd_dallas_unsol_event( > static const char *alc861vd_models[ALC861VD_MODEL_LAST] = { > [ALC660VD_3ST] = "3stack-660", > [ALC660VD_3ST_DIG] = "3stack-660-digout", > + [ALC660VD_V1S] = "v1s", > [ALC861VD_3ST] = "3stack", > [ALC861VD_3ST_DIG] = "3stack-digout", > [ALC861VD_6ST_DIG] = "6stack-digout", > @@ -13857,7 +13859,7 @@ static struct snd_pci_quirk alc861vd_cfg > SND_PCI_QUIRK(0x103c, 0x30bf, "HP TX1000", ALC861VD_HP), > SND_PCI_QUIRK(0x1043, 0x12e2, "Asus z35m", ALC660VD_3ST), > SND_PCI_QUIRK(0x1043, 0x1339, "Asus G1", ALC660VD_3ST), > - SND_PCI_QUIRK(0x1043, 0x1633, "Asus V1Sn", ALC861VD_LENOVO), > + SND_PCI_QUIRK(0x1043, 0x1633, "Asus V1S", ALC660VD_V1S), > SND_PCI_QUIRK(0x1043, 0x81e7, "ASUS", ALC660VD_3ST_DIG), > SND_PCI_QUIRK(0x10de, 0x03f0, "Realtek ALC660 demo", ALC660VD_3ST), > SND_PCI_QUIRK(0x1179, 0xff00, "Toshiba A135", ALC861VD_LENOVO), > @@ -13895,6 +13897,21 @@ static struct alc_config_preset alc861vd > .channel_mode = alc861vd_3stack_2ch_modes, > .input_mux = &alc861vd_capture_source, > }, > + [ALC660VD_V1S] = { > + .mixers = { alc861vd_lenovo_mixer }, > + .init_verbs = { alc861vd_volume_init_verbs, > + alc861vd_3stack_init_verbs, > + alc861vd_eapd_verbs, > + alc861vd_lenovo_unsol_verbs }, > + .num_dacs = ARRAY_SIZE(alc660vd_dac_nids), > + .dac_nids = alc660vd_dac_nids, > + .dig_out_nid = ALC861VD_DIGOUT_NID, > + .num_channel_mode = ARRAY_SIZE(alc861vd_3stack_2ch_modes), > + .channel_mode = alc861vd_3stack_2ch_modes, > + .input_mux = &alc861vd_capture_source, > + .unsol_event = alc861vd_lenovo_unsol_event, > + .init_hook = alc861vd_lenovo_automute, > + }, > [ALC861VD_3ST] = { > .mixers = { alc861vd_3st_mixer }, > .init_verbs = { alc861vd_volume_init_verbs, >

1 0

[alsa-devel] hda-intel - Add digout to ALC880 F1734 model
by Michael Gruber 05 Nov '08

05 Nov '08

Backstory: The patch "ALSA: hda - Add infrastructure for dynamic stream allocation" http://git.alsa-project.org/?p=alsa-kmirror.git;a=commit;h=ae32c9fe811fed22… broke the detection of my card. With this patch applied the dmesg output is: [ 3761.464838] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 3761.464863] PCI: Setting latency timer of device 0000:00:1b.0 to 64 [ 3761.499927] ACPI: PCI interrupt for device 0000:00:1b.0 disabled [ 3761.499945] HDA Intel: probe of 0000:00:1b.0 failed with error -22 When I loaded the module with model=... then it would work only for some models, but not for others. I found out that the ones which worked were the ones with a digout. I added the digout to the F1734 model and now it is working again. I can't test if the digout is really working because I lack the hardware, but when I turn on the IEC958 control in the mixer then red light is emitted from my headphone port. I will attach a patch that adds digout to this model because this seems the right thing to do, but I don't know whether there is something wrong with the aforementioned patch that caused my problem in the first place.

2 9

[alsa-devel] Monitoring ALSA's write pointer (appl_ptr)?
by brian-welch＠cox.net 05 Nov '08

05 Nov '08

Hello List, My first post, so excuse any ignorance. Is there a definitive/safe way to monitor ALSA's write pointer in the dma_area? It seems like the ack callback and the appl_ptr is the correct way, but I was told by another developer that appl_ptr doesn't work in all cases. As a future optimization for my hardware, I may want to tell ALSA to use a specific area of physical memory for it's dma_area, what is the best way to do that? Thanks, Brian

3 2

[alsa-devel] Mic threshold trigger
by OrazioPirataDelloSpazio (Lorenzo) 05 Nov '08

05 Nov '08

Hello, I would like to create a simple trigger from a microphone input, using alsa. For example I would like that every time I short-circuit a jack inserted in the "mic hole", my program say "Hello World". I would like that this application will be lightweight (I don't need audio quality, just a trigger!) and that cohexists with other apps that should keep using the output of the same sound card. My idea was to simply code a raw "snd_pcm_readi" call and after compare each sample of the captured block with a threshold. For instance, if the 90% of sample are above the given threshold, the trigger must act. Of course it doesn't work :-) I plug a simple jack in the mic, and open or short-circuit the poles. In the captured block, I can find only samples between 0xFFE0 and 0xFFFF (and some sporadic 0x0000). Any hits? Thanks Lorenzo

1 0

[alsa-devel] Current state of HDMI audio with nvidia graphics card ?
by Travis Place 04 Nov '08

04 Nov '08

Hi all, So i have 2 machines with nvidia VIDEO cards with HDMI outputs, and HDA-Intel sound cards.. i cant get HDMI audio to work on either.. IIRC, we currently need nvidia binary driver 177.80 (or above, if available), but what ALSA tree do we need ? sound-unstable ? latest GIT ? Has anyone heard any reports of nvidia hmdi audio working at all ? Thanks, Travis Place (wishie)

2 1

[alsa-devel] ALSA: ASoC codec: remove unused #include <version.h>
by Huang Weiyi 04 Nov '08

04 Nov '08

The file(s) below do not use LINUX_VERSION_CODE nor KERNEL_VERSION. sound/soc/codecs/ad73311.c This patch removes the said #include <version.h>. Signed-off-by: Huang Weiyi <weiyi.huang(a)gmail.com> diff --git a/sound/soc/codecs/ad73311.c b/sound/soc/codecs/ad73311.c index 37af860..59c4c8f 100644 --- a/sound/soc/codecs/ad73311.c +++ b/sound/soc/codecs/ad73311.c @@ -15,7 +15,6 @@ #include <linux/init.h> #include <linux/module.h> -#include <linux/version.h> #include <linux/kernel.h> #include <linux/device.h> #include <sound/core.h>

3 2

[alsa-devel] Issues with Fujitsu Siemens Amilo PA 1510 laptop
by Travis Place 04 Nov '08

04 Nov '08

2 1

Re: [alsa-devel] [PATCH 1/3] saa7146: Emagic Audiowerk8 low-level ALSA driver
by matthias.nyffenegger＠bluewin.ch 04 Nov '08

04 Nov '08

Hi Takashi, I fixed all of your findings except for the following where i have some questions: >> +/** >> + * >> + * PCI specific stuff >> + * >> + */ >> + >> +/** >> + * Organisation of EEPROM of the SAA7146A: >> + * The data of the subsystem ID and the subsystem vendor ID is organized in >> + * the EEPROM in the following order: >> + * >> + * EE-Addr Value Configuration Space Addr. >> + * --------------------------------------------------------------------- >> + * 00 Subsys ID (high byte) 2C, bits: 31 - 24 >> + * 01 Subsys ID (low byte) 2C, bits: 23 - 16 >> + * 02 Subsys Vendor ID (high byte) 2C, bits: 15 - 8 >> + * 03 Subsys Vendor ID (low byte) 2C, bits: 7 - 0 >> + * 04 Max_Lat 3C, bits: 31 - 24 >> + * 05 Min_Gnt 3C, bits: 23 - 16 >> + * >> + * For AW8 Subsys ID and Subsys Vendor ID are 0xFF on my card. >> + * For AW2 Subsys ID and Subsys Vendor ID are 0x00 on my card. >> + */ >> + >> +static struct pci_device_id snd_aw_ids[] = { >> + { PCI_VENDOR_ID_PHILIPS, PCI_DEVICE_ID_PHILIPS_SAA7146, >> + PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, }, > >We have a bad problem here. >As mentioned, there are other drivers with the very same device >and the very same PCI ID. >Since your driver doesn't check the availability of the hardware >in some way at probe, it loads even for a video device. >The same problem is present in the existing snd-aw2 driver, and we >need to find out the solution. Obviously the Audiowerk Soundcards cannot reliably be recognized by simply looking at the Subsystem-IDs because they're not unique values. I can see a chance here to probe i2c-bus for onboard EEPROM (AW2 and AW8) and/or onboard PLL (AW8) but I'm not sure whether or not this actually solves the problem for good. Another approach I see is that e.g. SuSE YaST supports loading a module for a specific pci slot - I don't know whether or not this is common use in other distros as well. How do you think about it? >> +enum states {disabled, enabled}; > >Ditto. This should be really a bool. I used to have more than these two states here and might add new states again in the future: that is why I would rather go for the enum type here. Regards, Matthias

1 0

[alsa-devel] [PATCH] hda: make a STAC_DELL_EQ option
by Matthew Ranostay 03 Nov '08

03 Nov '08

Add support for explicitly enabling the EQ distortion hack for systems without software biquad support. Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> --- diff --git a/pci/hda/patch_sigmatel.c b/pci/hda/patch_sigmatel.c index c2f900f..2c0f37f 100644 --- a/pci/hda/patch_sigmatel.c +++ b/pci/hda/patch_sigmatel.c @@ -70,6 +70,7 @@ enum { enum { STAC_92HD73XX_REF, STAC_DELL_M6, + STAC_DELL_EQ, STAC_92HD73XX_MODELS }; @@ -792,9 +793,7 @@ static struct hda_verb dell_eq_core_init[] = { }; static struct hda_verb dell_m6_core_init[] = { - /* set master volume to max value without distortion - * and direct control */ - { 0x1f, AC_VERB_SET_VOLUME_KNOB_CONTROL, 0xec}, + { 0x1f, AC_VERB_SET_VOLUME_KNOB_CONTROL, 0xff}, /* setup audio connections */ { 0x0d, AC_VERB_SET_CONNECT_SEL, 0x00}, { 0x0a, AC_VERB_SET_CONNECT_SEL, 0x01}, @@ -1622,11 +1621,13 @@ static unsigned int dell_m6_pin_configs[13] = { static unsigned int *stac92hd73xx_brd_tbl[STAC_92HD73XX_MODELS] = { [STAC_92HD73XX_REF] = ref92hd73xx_pin_configs, [STAC_DELL_M6] = dell_m6_pin_configs, + [STAC_DELL_EQ] = dell_m6_pin_configs, }; static const char *stac92hd73xx_models[STAC_92HD73XX_MODELS] = { [STAC_92HD73XX_REF] = "ref", [STAC_DELL_M6] = "dell-m6", + [STAC_DELL_EQ] = "dell-eq", }; static struct snd_pci_quirk stac92hd73xx_cfg_tbl[] = { @@ -4274,12 +4275,17 @@ again: sizeof(stac92hd73xx_dmux)); switch (spec->board_config) { - case STAC_DELL_M6: + case STAC_DELL_EQ: spec->init = dell_eq_core_init; + /* fallthru */ + case STAC_DELL_M6: spec->num_smuxes = 0; spec->mixer = &stac92hd73xx_6ch_mixer[DELL_M6_MIXER]; spec->amp_nids = &stac92hd73xx_amp_nids[DELL_M6_AMP]; spec->num_amps = 1; + + if (!spec->init) + spec->init = dell_m6_core_init; switch (codec->subsystem_id) { case 0x1028025e: /* Analog Mics */ case 0x1028025f: @@ -4289,8 +4295,6 @@ again: break; case 0x10280271: /* Digital Mics */ case 0x10280272: - spec->init = dell_m6_core_init; - /* fall-through */ case 0x10280254: case 0x10280255: stac92xx_set_config_reg(codec, 0x13, 0x90A60160);

2 3

[alsa-devel] Driver: EMU USB 0404 driver development
by Klaus Schulz 03 Nov '08

03 Nov '08

Hi folks. I learned that EMU handed over specs related to the EMU 0202/0404 USB to you guys some time ago. http://ubuntuforums.org/showpost.php?p=4892734&postcount=157 Is anybody assigned to the task? Cheers

4 8