ASoC: nau8822: Don't reconfigure PLL to the same values
Mark Brown
maintainerPATCH 1/1 ASoC: nau8822: Don't reconfigure PLL to the same values
When we configure the PLL record the input and output frequency, then if we get asked to configure the same values again just skip reprogramming the hardware. This makes things a bit easier to use for machine drivers since it means they don't need to keep track of if they've programmed the PLL so much.
--- sound/soc/codecs/nau8822.c | 7 +++++++ sound/soc/codecs/nau8822.h | 2 ++ 2 files changed, 9 insertions(+)
sound/soc/codecs/nau8822.c +7 -0
@@ -726,6 +726,10 @@ static int nau8822_set_pll(struct snd_soc_dai *dai, int pll_id, int source,struct nau8822_pll *pll_param = &nau8822->pll;int ret, fs; +if (freq_in == pll_param->freq_in && + freq_out == pll_param->freq_out) +return 0 ; + fs = freq_out /256 ; ret =nau8822_calc_pll (freq_in, fs, pll_param);
@@ -762,6 +766,9 @@ static int nau8822_set_pll(struct snd_soc_dai *dai, int pll_id, int source,snd_soc_component_update_bits (component,NAU8822_REG_POWER_MANAGEMENT_1 ,NAU8822_PLL_EN_MASK ,NAU8822_PLL_ON ); + pll_param->freq_in = freq_in; + pll_param->freq_out = freq_out; +return 0 ; }
sound/soc/codecs/nau8822.h +2 -0
@@ -198,6 +198,8 @@ struct nau8822_pll {int mclk_scaler;int pll_frac;int pll_int; +int freq_in; +int freq_out; };/* Codec Private Data */
Signature · 1 line
2.30.2
Mark Brown
maintainerQuoted 8 lines · Mark Brown
When we configure the PLL record the input and output frequency, then if we get asked to configure the same values again just skip reprogramming the hardware. This makes things a bit easier to use for machine drivers since it means they don't need to keep track of if they've programmed the PLL so much.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: nau8822: Don't reconfigure PLL to the same values
commit: 3ae190edc5f6f64f296f8dd15f4b511f529ab402
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark