From: Jack Mitchell <ml@embed.me.uk>
To: alsa-devel@alsa-project.org
Subject: tlv320aic3x regcache issue
Date: Wed, 26 Feb 2014 17:11:05 +0000 [thread overview]
Message-ID: <530E2029.6090904@embed.me.uk> (raw)
Hi,
I have come across an issue where the regcache mechanism used in the
tlv320aic3x driver is causing problems. When switching from 44.1khz to
48khz some of the registers are not written due to the default register
cache holding the same value as being written. However, the codec
requires these registers to be written in order to trigger the change,
this has been proven by changing the register default to something
different, therefore forcing a write at the correct time and it triggers
the change as expected.
What would be the best way to force these registers to be written? Is
there some sort of force write flag, or a way to turn off the cache just
during this portion of the configuration?
Any direction in the proper way of doing this would be much appreciated.
Cheers,
Jack
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
next reply other threads:[~2014-02-26 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 17:11 Jack Mitchell [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-26 19:13 tlv320aic3x regcache issue Jack Mitchell
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=530E2029.6090904@embed.me.uk \
--to=ml@embed.me.uk \
--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