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

[alsa-devel] [PATCH] ppc-beep - switch to using input_dev->dev.parent
by Dmitry Torokhov 08 May '07

08 May '07

In preparation for struct class_device -> struct device input core conversion, switch to using input_dev->dev.parent when specifying device position in sysfs tree. Also, do not access input_dev->private directly, use helpers. Signed-off-by: Dmitry Torokhov <dtor(a)mail.ru> --- sound/ppc/beep.c | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) Index: work/sound/ppc/beep.c =================================================================== --- work.orig/sound/ppc/beep.c +++ work/sound/ppc/beep.c @@ -118,7 +118,7 @@ static int snd_pmac_beep_event(struct in default: return -1; } - chip = dev->private; + chip = input_get_drvdata(dev); if (! chip || (beep = chip->beep) == NULL) return -1; @@ -239,8 +239,8 @@ int __init snd_pmac_attach_beep(struct s input_dev->evbit[0] = BIT(EV_SND); input_dev->sndbit[0] = BIT(SND_BELL) | BIT(SND_TONE); input_dev->event = snd_pmac_beep_event; - input_dev->private = chip; - input_dev->cdev.dev = &chip->pdev->dev; + input_dev->dev.parent = &chip->pdev->dev; + input_set_drvdata(input_dev, chip); beep->dev = input_dev; beep->buf = dmabuf; @@ -251,8 +251,8 @@ int __init snd_pmac_attach_beep(struct s err = snd_ctl_add(chip->card, beep_ctl); if (err < 0) goto fail1; - - chip->beep = beep; + + chip->beep = beep; err = input_register_device(beep->dev); if (err)

1 0

[alsa-devel] Fwd: [Alsa-devel] Read the input of a soundcard with ALSA
by Nyx 07 May '07

07 May '07

Hi, I have some problems to read the input of my soundcard using Alsa and I don't really understand how to have access to the input of my soundcard. I follow : http://www.alsa-project.org/alsa-doc/alsa-lib/_2test_2pcm_8c-example.html http://www.alsa-project.org/alsa-doc/alsa-lib/_2test_2latency_8c-example.ht… # So, in my program, I have created two handles for capture and playback : char *device = "hw:0,0"; snd_output_t *output; snd_input_t *input; snd_pcm_t *phandle, *chandle; # then I connect the phandle to the out err = snd_output_stdio_attach(&output, stdout, 0); if (..) # Do I have to connect the chandle with the input ? # err = snd_input_stdio_attach(&input, stdin, 0); # I open the access to PCM err = snd_pcm_open(&phandle, pdevice, SND_PCM_STREAM_PLAYBACK, 0) if (..) err = snd_pcm_open(&chandle, pdevice, SND_PCM_STREAM_CAPTURE, 0) if(..) # Hardware and software Parameters ## Hardware Parameters snd_pcm_hw_params; int err; err = snd_pcm_hw_params_any(phandle, params); if(..); err = snd_pcm_hw_params_set_access(phandle, params,SND_PCM_ACCESS_RW_INTERLEAVED); if(..); err = snd_pcm_hw_params_set_format(phandle, params,SND_PCM_FORMAT_S16); if(..); err = snd_pcm_hw_params_set_channels(phandle, params, 1); if(..); err = snd_pcm_hw_params_set_rate_near(phandle, params, 44100, 0); if(..); err = snd_pcm_hw_params_set_buffer_time_near(phandle, params, 500000, &dir); if(..); err = snd_pcm_hw_params_set_time_near(phandle, params, 100000, &dir), if(..); err = snd_pcm_hw_params(phandle, params); ##Software parameters err = snd_pcm_sw_params(phandle, params); if(..); err = snd_pcm_sw_params_set_start_threshold(phandle, swparams, 0x7fffffff); if(..); err = snd_pcm_sw_params_set_avail_min(phandle, swparams, 4); # same configuration for phandle # Link output to input and start err = snd_pcm_link(chandle, phandle); if(..); err = snd_pcm_start(chandle); if(..); #Then I want to read my input frames_in = 0; in_max = 0; latency = 28; buffer = malloc((latency_max * snd_pcm_format_width(format) / 8) * 2); while (1) { r = readbuf(chandle, buffer, latency, &frames_in, &in_max)); if(..); } # description of the function long readbuf(snd_pcm_t *handle, char *buf, long len, size_t *frames, size_t *max) { long r; do { r = snd_pcm_readi(handle, buf, len); } while (r == -EAGAIN); if (r > 0) { *frames += r; if ((long)*max < r) *max = r; } printf ("r = %s, len %li and buf[%d] %f \r", snd_strerror(r), len,i, buf[i]); return r; } So I compile it and I run it, and I have $ read = Broken Pipe, len = 28 and buf[..] = 0.000 Anyone can help me to read the input of my sound card ? Thank you -- K PS : if I sent this message twice, excuse-me. I haven't confirm my subscription the first time

2 3

[alsa-devel] [PATCH] Add sequence parsing for speaker-outs in snd_hda_parse_pin_def_config()
by Steve Longerbeam 07 May '07

07 May '07

2 2

Re: [alsa-devel] Getting Started on Alsa
by Ash Willis 07 May '07

07 May '07

Hi Chris, > I'd like to take action on bug #305, since it's my own itch. I've done very > low-level programming, but not on Linux device drivers. I'm very familiar > with command line development tools. > If you're not familiar with drivers or audio drivers in particular then reading Writing an ALSA Driver by Takashi Iwai might be a good place to start. You're referring to the suspend/resume bug in the cs46xx driver, right? Maybe try dumping all the registers while it's working and dumping them while it's broken and comparing the two sets of data? I guess the suspend function is doing something that it shouldn't be, or the resume function isn't doing something that it should be...good luck on finding out what that is. Ash =

3 2

Re: [alsa-devel] Getting Started on Alsa
by Ash Willis 07 May '07

07 May '07

> Thanks for the tips, Ash. I've found the Iwai document. Now there's some > light reading. I take it that it's still relevant, even though it hasn't > been updated since 2005. > I haven't actually read it since 2005 I'm afraid :) but I don't think anything's changed that drastically. The fundamentals are all there. > Yes, the cs46xx driver. That chip is in a lot of machines (at least ten > ThinkPad models), and with this bug nobody running Alsa likes Linux very > much. > Yeah, it's a pretty poor show that this bug has existed for so long. Let's hope you can zap it! > Is there some (handy) way to dump the registers from DOS or Windows as a > comparison? > Well, that depends. I'm not familiar with the hardware. There's a Windows program called PCItree. It allows you to view the current status of the ioport of a chosen device. Now, that's pretty handy if the regs for the card are mapped directly onto the io port. It's usually the case though, I think, that the registers aren't just mapped on and you'll need to query the card. If they're not mapped onto the io port (and forgive me again - not familiar with this chip) then you could use a debugger such as Numega SoftIce to manually issue queries to find out the contents of the registers. Sounds like a happy fun time. Writing the code to do a reg dump might be fun too. You may also want to use a debugger/disassembler with Windows (or other) drivers in order to find out what those drivers do to the card on resume. > For development: Since the drivers go into the kernel, I should be able to > find a page on getting a development environment set up... right? I'm You don't need to mess with the kernel as ALSA is available as a package. All you really need is the latest copy of alsa-driver and a compiler and you're good to go. Ash =

1 0

[alsa-devel] 1.0.14~rc4 prepared for upload.
by Elimar Riesebieter 06 May '07

06 May '07

As the compile errors in alsa-lib fixed I've preparded 1.0.14~rc4 (svn r1849) for upload: alsa-driver alsa-lib alsa-oss alsa-plugins alsa-utils alsa-tools stays still as 1.0.13~rc3. Jordi, could you please upload? Now I go for a beer ;) Elimar -- You cannot propel yourself forward by patting yourself on the back.

1 1

[alsa-devel] Getting Started on Alsa
by Chris Schumann 06 May '07

06 May '07

Hello, I'd like to take action on bug #305, since it's my own itch. I've done very low-level programming, but not on Linux device drivers. I'm very familiar with command line development tools. Is there any documentation on how to get started doing bugfixes or development for Alsa, or do I just look for source and start hacking? Thanks, Chrs

1 0

[alsa-devel] [PATCH] hda_codec: restore control element values during resume
by Daniel Drake 06 May '07

06 May '07

After resume from suspend-to-RAM, there is no sound output from my Intel HDA hardware: 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) Found in a Dell Inspiron 640m, SigmaTel STAC9200 chip. After resuming, sound immediately returns when you adjust the volume one notch in either direction. I reported this on the ALSA bug tracker (#0002989). Further investigation shows that the AC_VERB_SET_AMP_GAIN_MUTE verb is not being executed during resume, which seems strange. Does other hardware really store this value during a suspend/resume cycle? Or maybe the volume is generally controlled through other means on other setups? I'm not entirely sure what the difference is between kcontrol and kcontrol_new structures, but I note that there is already some code to restore the values for kcontrol_new elements. I solved the issue with the following patch. Is it correct? Signed-off-by: Daniel Drake <dsd(a)gentoo.org> Index: linux-2.6/sound/pci/hda/hda_codec.c =================================================================== --- linux-2.6.orig/sound/pci/hda/hda_codec.c +++ linux-2.6/sound/pci/hda/hda_codec.c @@ -2248,15 +2248,39 @@ EXPORT_SYMBOL(snd_hda_suspend); int snd_hda_resume(struct hda_bus *bus) { struct list_head *p; + struct snd_ctl_elem_value *val = kmalloc(sizeof(*val), GFP_KERNEL); + + if (!val) + return -ENOMEM; list_for_each(p, &bus->codec_list) { struct hda_codec *codec = list_entry(p, struct hda_codec, list); + struct snd_kcontrol *kctl; + + codec->in_resume = 1; + hda_set_power_state(codec, codec->afg ? codec->afg : codec->mfg, AC_PWRST_D0); + + + list_for_each_entry(kctl, &bus->card->controls, list) { + memset(val, 0, sizeof(*val)); + val->id = kctl->id; + /* Assume that get callback reads only from cache, + * not accessing the real hardware + */ + if (snd_ctl_elem_read(bus->card, val) < 0) + continue; + snd_ctl_elem_write(bus->card, NULL, val); + } + if (codec->patch_ops.resume) codec->patch_ops.resume(codec); + + codec->in_resume = 0; } + kfree(val); return 0; }

2 4

[alsa-devel] New Soundcard Matrix
by Jaroslav Kysela 05 May '07

05 May '07

Hello all, I moved the contents of matrix from XML files to Wiki - see http://bugtrack.alsa-project.org/main/index.php/Matrix:Main Please, no more updates to old matrix now. I left the information structure (we can update it later): Vendor -> Device -> ALSA Module If any volunteers are watching this list, we have many "wanted" pages now: http://bugtrack.alsa-project.org/main/index.php/Special:Wantedpages Example page for Matrix:Tag-* : http://bugtrack.alsa-project.org/main/index.php?title=Matrix:Tag-PCI&action… Example page for Matrix:Module-* : http://bugtrack.alsa-project.org/main/index.php?title=Matrix:Module-ali5451… Jaroslav ----- Jaroslav Kysela <perex(a)suse.cz> Linux Kernel Sound Maintainer ALSA Project, SUSE Labs

1 0

Re: [alsa-devel] Wiki Site
by Jaroslav Kysela 05 May '07

05 May '07

On Fri, 4 May 2007, cameron porter wrote: > Greetings, > > I noticed the notice on your front page needing people to help transfer the > site contents over to your wiki that you set up. I did a little bit of work, > and managed to get a navigation, downloads page, application page, and some > other links. Your work is greatly appreciated here. > I would be glad to continue, if you think I am doing things right. The next > thing I had planned to make some changes to was the documentation section, > add a changes section, add a structure whereby you have an article for each > package, and then the folder for that package contains all the different > versions that have been or will be released. Please give me any thoughts on > any of these, and tell me if you think they are a good idea, and whether I > should continue or not. We need to move the contents at first, but I agree that a good page structure should be created during this process. Please, go ahead - the nice thing on wiki is that we can rearrange information later (if we find a problem with the structure). I just started to move probably most problematic part - soundcard matrix to wiki. Thanks, Jaroslav ----- Jaroslav Kysela <perex(a)suse.cz> Linux Kernel Sound Maintainer ALSA Project, SUSE Labs

1 0