lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID:  <471606A5.90807@endrelia.com>
Date:	Wed, 17 Oct 2007 08:57:09 -0400
From:	Frank Mandarino <fmandarino@...relia.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject:  Re: audio codec control

Pierre Savary wrote:
> Hello,
> 
> thank you for your help about my previous request concerning a problem in
> audio capture on CS42L51 codec. 
> 
> For your information, my problem came from a bad configuration of an ARM9
> register. As my register settings, the capture had to start with an event on
> RD pin, which is not connected with the codec on my board. Setting the START
> bits to 0 = "continuous" solved my problem.
> 
> Today, I need some more help to understand how your driver is used from an
> external application. Notably, how do you call the controls "Master Playback
> Volume", "Master Playback ZC Switch", "Capture Volume", etc, but also the
> "Input Select" and "Output Mixer", for example ?
> Shouldn't we modify the field at91_pcm_ops->ioctl (in
> /sound/soc/at91/at91-pcm.c), which is now set to the common function
> snd_pcm_lib_ioctl, in order to launch codec-related commands ?
> 
> Thank you in advance for your help.
> 
> 
> Sylvain
> 
> 
> -------------------------------------------------------------------
> List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
> FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
> Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php
> 

Pierre and/or Sylvain,

I'm not sure how you call the controls from an external application.  I
have only used the alsa-utils amixer command to set the controls, and
alsactl to save the settings in /etc/asound.state and then restore them
at boot.

So you could look at the amixer source to see how they are called.

The available controls are normally defined in the ASoC codec driver,
and you shouldn't need to modify the at91_pcm_ops->ioctl pointer to
access them.

../fam
-- 
Frank Mandarino                                fmandarino(a)endrelia.com
Endrelia Technologies Inc.
Toronto, Ontario, Canada

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ