[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1615829492-8972-1-git-send-email-spujar@nvidia.com>
Date: Mon, 15 Mar 2021 23:01:30 +0530
From: Sameer Pujar <spujar@...dia.com>
To: <broonie@...nel.org>, <lgirdwood@...il.com>
CC: <oder_chiou@...ltek.com>, <michael@...le.cc>,
<jonathanh@...dia.com>, <kuninori.morimoto.gx@...esas.com>,
<alsa-devel@...a-project.org>, <linux-kernel@...r.kernel.org>,
<linux-tegra@...r.kernel.org>, <thierry.reding@...il.com>,
<sharadg@...dia.com>, Sameer Pujar <spujar@...dia.com>
Subject: [PATCH 0/2] Do not handle MCLK device clock in simple-card-utils
With commit 1e30f642cf29 ("ASoC: simple-card-utils: Fix device module clock")
simple-card-utils can control MCLK clock for rate updates or enable/disable.
But this is breaking some platforms where it is expected that codec drivers
would actually handle the MCLK clock. One such example is following platform.
- "arch/arm64/boot/dts/freescale/fsl-ls1028a-kontron-sl28-var3-ads2.dts"
In above case codec, wm8904, is using internal PLL and configures sysclk
based on fixed MCLK input. In such cases it is expected that, required PLL
output or sysclk, is just passed via set_sysclk() callback and card driver
need not actually update MCLK rate. Instead, codec can take ownership of
this clock and do the necessary configuration.
So the original commit is reverted and codec driver for rt5659 is updated
to fix my board which has this codec.
Sameer Pujar (2):
ASoC: simple-card-utils: Do not handle device clock
ASoC: rt5659: Update MCLK rate in set_sysclk()
sound/soc/codecs/rt5659.c | 5 +++++
sound/soc/generic/simple-card-utils.c | 13 +++++++------
2 files changed, 12 insertions(+), 6 deletions(-)
--
2.7.4
Powered by blists - more mailing lists