Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755725AbdLTPus (ORCPT ); Wed, 20 Dec 2017 10:50:48 -0500 Received: from heliosphere.sirena.org.uk ([172.104.155.198]:59264 "EHLO heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755701AbdLTPuq (ORCPT ); Wed, 20 Dec 2017 10:50:46 -0500 Date: Wed, 20 Dec 2017 15:50:00 +0000 From: Mark Brown To: Olivier MOYSAN Cc: "lgirdwood@gmail.com" , "perex@perex.cz" , "tiwai@suse.com" , "mcoquelin.stm32@gmail.com" , Alexandre TORGUE , "alsa-devel@alsa-project.org" , "linux-arm-kernel@lists.infradead.org" , "kernel@stlinux.com" , "linux-kernel@vger.kernel.org" , Arnaud POULIQUEN , Benjamin GAIGNARD , "patches@opensource.wolfsonmicro.com" Subject: Re: [RFC PATCH 2/2] ASoC: select sysclk clock from mlck clock provider in wm8994 driver Message-ID: <20171220155000.GD17890@sirena.org.uk> References: <1513270438-18523-1-git-send-email-olivier.moysan@st.com> <1513270438-18523-3-git-send-email-olivier.moysan@st.com> <20171214173624.GM9788@sirena.org.uk> <43426b67-3546-8422-7fcb-9fa1ff192679@st.com> <20171219093506.GD8563@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XvKFcGCOAo53UbWW" Content-Disposition: inline In-Reply-To: X-Cookie: Neutrinos have bad breadth. User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1544 Lines: 41 --XvKFcGCOAo53UbWW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 20, 2017 at 12:42:10PM +0000, Olivier MOYSAN wrote: > As a generic machine, simple or audio graph cards are not able to manage= =20 > codec clock muxing. > If we exclude the management of muxing through codec controls, > the remaining solution is to handle it fully through clock framework. > The current patch only supports a limited range of muxing capabilities=20 > of the codec. > To have a full management of the muxing, I think it is necessary to add > a device tree node for each codec interface and to define an aif clock=20 > in these nodes. > Then parent clock assignment of these aif clocks would allow to handle=20 > the muxing. Controlling clocking through a clock API binding would be good, yes. That'd solve a bunch of other problems with use of multi-purpose clocks for audio as well. --XvKFcGCOAo53UbWW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlo6hqcACgkQJNaLcl1U h9DFOwf9EFd8OGa3Gc6X94wtf+ww6JRTcI+zcddC51bU18nM/k39xlGLTyCvqCcT HiTR3x3qQP1rUCbLOiKVIOARAu7JmhQAovhbzib4jJ1wIZdFov5gZecKX4c7E32G 1opjCwgZ8/tU5ClBfDaXvV6xvKEHPnzJ9oyo4jjFKIY2CxJMbwzBF4od+x2qjmsJ J60JrXPVT6H3LILm7o2Vut4/tlUN3QAHT0K6nYfXAE5OZVYEHQloLJjbax3EpQbp W6WqneVffaatVdIyUXsZMJyp7DM3EByj26cziJQ2cuyF02tg95qLIjqUmEP/Wxca 0sxBrWK8s8A6o0a0EycnoECWAk2+GQ== =ML+3 -----END PGP SIGNATURE----- --XvKFcGCOAo53UbWW--