[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b073a0513dd04d4b99177b2f2c3a8eb5@BY2PR03MB505.namprd03.prod.outlook.com>
Date: Thu, 23 Jan 2014 10:32:57 +0000
From: "Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>
To: Fabio Estevam <festevam@...il.com>
CC: Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Timur Tabi <timur@...i.org>,
"guangyu.chen@...escale.com" <guangyu.chen@...escale.com>,
Takashi Iwai <tiwai@...e.de>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: RE: [alsa-devel] [PATCH] ASoC: fsl-sai: convert to use regmap API
for Freeacale SAI
> > static int fsl_sai_set_dai_sysclk(struct snd_soc_dai *cpu_dai,
> > int clk_id, unsigned int freq, int dir)
> > {
> > - struct fsl_sai *sai = snd_soc_dai_get_drvdata(cpu_dai);
> > int ret;
> >
> > if (dir == SND_SOC_CLOCK_IN)
> > return 0;
> >
> > - ret = clk_prepare_enable(sai->clk);
> > - if (ret)
> > - return ret;
>
> The clock related change seems unrelated to the usage of regmap, right?
>
The clock operations in the driver is only related to the module clock, and has
move to the regmap core and regmap core will to the same clock operations at
proper time, since we are using:
+ sai->regmap = devm_regmap_init_mmio_clk(&pdev->dev,
+ "sai", base, &fsl_sai_regmap_config);
Thanks,
Best Regards,
Xiubo
Powered by blists - more mailing lists