From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Dimitris Papavasiliou <dpapavas@gmail.com>
Subject: Re: Need help fixing pop/click artifacts in an ASOC driver
Date: Mon, 17 Dec 2018 12:08:36 -0600 [thread overview]
Message-ID: <273cb3d8-7cd6-867a-ebb4-22217f88e0a8@linux.intel.com> (raw)
In-Reply-To: <20181217173930.GF27909@sirena.org.uk>
On 12/17/18 11:39 AM, Mark Brown wrote:
> On Mon, Dec 17, 2018 at 09:03:33AM -0600, Pierre-Louis Bossart wrote:
>
>> I started prototyping a different approach where the codec driver passes the
>> regmap information to the clock driver. What's missing in the patchset is
>> the addition of a clock control in the machine driver, and logic added so
>> that rate change can only be done in a hw_params if there was a complete
>> stop and reset on a DAPM_OFF event. compile-tested only for now.
>> https://github.com/plbossart/sound/commits/hifiberry/clks
> That looks a lot like the CODEC should be exporting a GPIO driver so the
> machine driver doesn't actually need the regmap? The only register
> touched is _GPIO_CONTROL_1.
I am not sure what you meant by 'exporting a GPIO driver' (mostly
because I am not familiar with any GPIO framework) but indeed the local
oscillator choice is controlled by a single register accessible through
regmap - and changes to that register should only happen when the device
is a specific state to prevent click/pops.
The machine driver should use clk_set_rate() and not directly handle
regmap or codec stuff. If it does, or if the clock framework isn't
relevant here then we can simplify all this as suggested in
https://patchwork.kernel.org/patch/10444387/. What I was trying to do
with the github update is to keep the clock framework, tie it closer
with the codec parts with a state variable that prevents wild changes
without going back to a 'safe' idle state (similar idea as PulseAudio
clock changes, which can only happen when the PCM is not opened and used).
next prev parent reply other threads:[~2018-12-17 18:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 16:37 Need help fixing pop/click artifacts in an ASOC driver Dimitris Papavasiliou
2018-11-08 1:42 ` Pierre-Louis Bossart
2018-11-08 15:18 ` Takashi Iwai
2018-11-10 15:46 ` Dimitris Papavasiliou
2018-11-14 22:06 ` Mark Brown
2018-11-14 22:50 ` Dimitris Papavasiliou
2018-11-14 23:02 ` Mark Brown
2018-11-14 23:55 ` Dimitris Papavasiliou
2018-11-15 0:33 ` Mark Brown
2018-11-15 11:25 ` Dimitris Papavasiliou
2018-11-15 19:04 ` Mark Brown
2018-11-18 13:37 ` Dimitris Papavasiliou
2018-11-24 20:17 ` Dimitris Papavasiliou
2018-12-13 17:42 ` Mark Brown
2018-12-17 12:17 ` Dimitris Papavasiliou
2018-12-17 12:37 ` Mark Brown
2018-12-17 12:58 ` Dimitris Papavasiliou
2018-12-17 14:10 ` Mark Brown
2018-12-17 15:03 ` Dimitris Papavasiliou
2018-12-17 15:40 ` Mark Brown
2018-12-17 16:23 ` Dimitris Papavasiliou
2018-12-17 16:52 ` Mark Brown
2018-12-18 10:39 ` Dimitris Papavasiliou
2018-12-19 16:19 ` Mark Brown
2018-12-19 21:44 ` Dimitris Papavasiliou
2018-12-20 15:36 ` Mark Brown
2018-12-20 20:41 ` Dimitris Papavasiliou
2018-12-21 10:57 ` Mark Brown
2018-12-21 13:05 ` Dimitris Papavasiliou
2018-12-21 17:33 ` Mark Brown
2018-12-23 20:11 ` Dimitris Papavasiliou
2018-12-22 14:44 ` Matthias Reichl
2018-12-23 20:15 ` Dimitris Papavasiliou
2018-12-17 15:03 ` Pierre-Louis Bossart
2018-12-17 17:39 ` Mark Brown
2018-12-17 18:08 ` Pierre-Louis Bossart [this message]
2018-12-17 19:02 ` Mark Brown
2018-12-17 19:14 ` Pierre-Louis Bossart
2019-01-05 19:01 ` Pierre-Louis Bossart
2018-12-18 11:32 ` Dimitris Papavasiliou
2018-12-18 14:12 ` Pierre-Louis Bossart
2018-12-18 17:10 ` Dimitris Papavasiliou
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=273cb3d8-7cd6-867a-ebb4-22217f88e0a8@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dpapavas@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.