[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DtpoH0dLDX3=Sv4UUpX_=66VEZPsJUWQNnYviApfMLKQ@mail.gmail.com>
Date: Thu, 19 May 2022 10:23:06 -0300
From: Fabio Estevam <festevam@...il.com>
To: Shengjiu Wang <shengjiu.wang@....com>
Cc: Nicolin Chen <nicoleotsuka@...il.com>,
Xiubo Li <Xiubo.Lee@...il.com>,
Shengjiu Wang <shengjiu.wang@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Linux-ALSA <alsa-devel@...a-project.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: fsl_sai: Enable MCTL_MCLK_EN bit for master mode
Hi Shengjiu,
On Thu, May 19, 2022 at 9:49 AM Shengjiu Wang <shengjiu.wang@....com> wrote:
> diff --git a/sound/soc/fsl/fsl_sai.c b/sound/soc/fsl/fsl_sai.c
> index fa950dde5310..dae16a14f177 100644
> --- a/sound/soc/fsl/fsl_sai.c
> +++ b/sound/soc/fsl/fsl_sai.c
> @@ -437,6 +437,12 @@ static int fsl_sai_set_bclk(struct snd_soc_dai *dai, bool tx, u32 freq)
> FSL_SAI_CR2_DIV_MASK | FSL_SAI_CR2_BYP,
> savediv / 2 - 1);
>
> + if (sai->soc_data->max_register >= FSL_SAI_MCTL) {
Isn't it a bit fragile to take this decision based on the number of
SAI registers in the SoC?
What about adding a specific field in soc_data for such a purpose?
Powered by blists - more mailing lists