Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752692AbcDZLoo (ORCPT ); Tue, 26 Apr 2016 07:44:44 -0400 Received: from mout.kundenserver.de ([217.72.192.73]:58286 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751986AbcDZLom (ORCPT ); Tue, 26 Apr 2016 07:44:42 -0400 From: Arnd Bergmann To: Peter Griffin Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, srinivas.kandagatla@gmail.com, maxime.coquelin@st.com, patrice.chotard@st.com, vinod.koul@intel.com, lee.jones@linaro.org, dmaengine@vger.kernel.org, devicetree@vger.kernel.org, broonie@kernel.org, ludovic.barre@st.com, arnaud.pouliquen@st.com Subject: Re: [PATCH 09/18] ASoC: sti: Update DT example to match the driver code Date: Tue, 26 Apr 2016 13:44:02 +0200 Message-ID: <5608365.uloflbeuqO@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20160426111532.GA5457@griffinp-ThinkPad-X1-Carbon-2nd> References: <1461236675-10176-1-git-send-email-peter.griffin@linaro.org> <6161197.8XCk69TI60@wuerfel> <20160426111532.GA5457@griffinp-ThinkPad-X1-Carbon-2nd> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:g1kj1iKnWkuP0hVd8sWJpEqMydPrbxE8PA/28ew1xG0IvmlFsJa 8tiTRzS4QdF7mdKYWYlEwcxiFN8wGXobGb4zXmGwOe5foLGsed9MHJbnQSeF6/rHhLnPGUi +WB86rx+uiZ4zH+rjE42FVibLI1GxKnGsm2SadTB75YwoeqJHaHvqeHJo5116zpz2dJrzNG BlWfjBU3RoEaKTpJBt0jw== X-UI-Out-Filterresults: notjunk:1;V01:K0:OfddymiENVk=:GNMLepVdUatAEUDmW/MS1a qwppBiUjcb3ZB9pIQZ11uBvuJ+PJVgnLzwNggMcyHWstMvYavY3vmwE+eicAmnOJMActaIpk5 HwwWn081eJKlfmnhYdaLaniYN5LJfD9Hh4wAaOz7UwA9n54YZLpz/Lv24wSQ2WHoT5cto85sO 54JvmUTKXH/2DrDq7SJsfDa6oCgFG7QTL2Wa+md4knqLHvjb8zpsDedqODKVsuAZ4KfSodQxb fw5eVhwzyprYsVtG98TqCpM1hcTsiC6r8Kcc+M1V1mZWhwSj2odwbamFH8BrdtWqF7V2/sMS1 Dv1N88gqMzM35dFaOc5sJpwHg5njwBgOGrCc9zFrXjqvEHi91emMPDHr2g9Guj2V93IUhtcF7 zCy/SEX0sx0Ecj/fRFOaq85U8paiUQLREWLUT1zhuwJM9Hdn/OkvCwcv7/l3GNOnoK/93dD0W vhwY3eup8BqvYrdNA7GC68aQadyrpB9lvfEfEbPOzRKKFXMogTeZxSIPSf07jG4IA2XXYTmQD 2lVgvVP7JF82Jmdy+0toNjQ+d/6dD7Z+BDEox4irz4mM2HW6pPeMQn4zlMHZtJR1w4oMEBdbj phyJZSbLqRS7dX/SJyk9TFB9FL6fy9juTyGNiyPjxHoefDtcQZzkIziXkDg6tP6ZC+bAOOKV5 Ske4C99IukCASzybEDH7WDsviuZ5lJNTZRQD1196J8TWtZaJzQY/ECXnMn83Ve2ubKdk89Qra DoyLiQ5qwrgpFs4R Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1015 Lines: 26 On Tuesday 26 April 2016 12:15:32 Peter Griffin wrote: > > > > > If not what would you recommend instead? > > > > It's still not clear to me what that bit in the syscfg register > > is for. Given the error message about "sti-audio-clk-glue", > > I suspect that this is actually a clock controller and that > > it should be using the clock binding with a separate driver > > instead of manipulating the regmap directly from the audio driver. > > Luckily I do have the datasheet for the audio-glue sysconf register. > > It says: - > > [11:8] PCM_CLK_SEL: Selects the frequency synthesizer clock or the external > PCM clock for each channel. > > The driver only ever sets this to 1 which selects the frequency synthesizer > clock. So the bitfield of the register which the driver is using (PCM_CLK_SEL) > is a clock mux. Ok, that sounds like it could be either a really simple clock driver with just a few lines, or integrated into an existing clock driver if you already have one for this syscon node. Arnd