From: Alban Browaeys <prahal@yahoo.com>
To: Alsa-devel@alsa-project.org
Subject: acer ferrari one hda realtek - attempt to improve forte mic IC support
Date: Thu, 19 Jan 2012 22:59:55 +0100 [thread overview]
Message-ID: <1327010395.22934.12.camel@argos.server.maison> (raw)
A lot of reports about aspire one issues lead me to think the mic IC
processing is the same as on this acer ferrari one 200.
Looking at alsa-driver-aspire_one-v1.09 assembly I see that it setup the
bdl entries to point to a capture buffer which it then split in two
buffers : namely mic and speaker .
This split happens by moving the first 32 bits to mic , the next 32 to
speaker , then to mic and so forth.
azx_pcm_hw formats is set to S16 LE.
I was wondering about the the 32 bits step between mic and speaker
buffer and ended up on azx_pcm_preapre where for the capture case
snd_hda_calc_stream_format is hardcoded a number of channels of 4.
My issue is I attempted the same trick and it seems I still miss
something . Ie the azx_dev->format passed in azx_setup_controller to
SD_FORMAT registry is incremented by 3 namely 0x33 . Though I still miss
half of each samples same as when I was passing runtime->channels ie 2
and 0x31.
The codec is ALC272X ATI SB.
Best regards,
Alban Browaeys
reply other threads:[~2012-01-19 22:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1327010395.22934.12.camel@argos.server.maison \
--to=prahal@yahoo.com \
--cc=Alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox