From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752598AbdIFTr1 (ORCPT ); Wed, 6 Sep 2017 15:47:27 -0400 Received: from mail-pf0-f174.google.com ([209.85.192.174]:36038 "EHLO mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751969AbdIFTrZ (ORCPT ); Wed, 6 Sep 2017 15:47:25 -0400 X-Google-Smtp-Source: ADKCNb798iuWgnAw0GZqBhI9kfkwSSU+nmrY5WW089K6sBT5FVVEuor9P6Wa+3TrpuicNCZLtIcMnQ== Date: Wed, 6 Sep 2017 12:47:49 -0700 From: Nicolin Chen To: =?utf-8?Q?=C5=81ukasz?= Majewski Cc: Fabio Estevam , Timur Tabi , Xiubo Li , Liam Girdwood , Mark Brown , Jaroslav Kysela , Takashi Iwai , "festevam@gmail.com" , "alsa-devel@alsa-project.org" , "linuxppc-dev@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] sound: soc: fsl: Do not set DAI sysclk when it is equal to system freq Message-ID: <20170906194748.GA31334@Asurada-Nvidia> References: <07e54d28-3bbc-aad2-146b-30867c0bc337@denx.de> <20170905052031.GB2774@Asurada-CZ80> <819784e1-910b-6833-997a-2097e147bd0c@denx.de> <20170905181108.GB23906@Asurada-Nvidia> <20170905225225.GA14132@Asurada-Nvidia> <20170906173348.GA28104@Asurada-Nvidia> <69352458-2e90-a847-2c2f-bba259a32162@denx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <69352458-2e90-a847-2c2f-bba259a32162@denx.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 06, 2017 at 08:35:50PM +0200, Ɓukasz Majewski wrote: > clocks = <&clks IMX6QDL_CLK_SSI2_IPG>, > <&clks IMX6QDL_CLK_SSI2>; > clock-names = "ipg", "baud"; > >> dailink_master: cpu { > >> sound-dai = <&ssi2>; > >> clock = <&SSSS>; > > If possible I do prefer a solution, which uses only DTS. > Side question - how to refer to baud clock from [1]? Just add a property to this cpu node like: clock = <&clks IMX6QDL_CLK_SSI2>; > >> system-clock-frequency = ; This would not be necessary unless you want to specify a clock rate so as to override the clock rate configuration in hw_params(). > >This is the right solution based on current simple-card driver. For > >SSI (having two clocks), you have to specify the baud clock in the > >cpu node like that. I believe this is what the simple-card designer > >expected users to do since the cpu node is the first place that the > >driver tries to look at. > > I will give a shoot the option with adding the ipg clock. No, not ipg clock. You should use the second clock -- baud clock.