From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932328AbcHKLes (ORCPT ); Thu, 11 Aug 2016 07:34:48 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:55470 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752039AbcHKLeq (ORCPT ); Thu, 11 Aug 2016 07:34:46 -0400 Date: Thu, 11 Aug 2016 12:34:32 +0100 From: Mark Brown To: Pierre-Louis Bossart Cc: Vinod Koul , mark.rutland@arm.com, oder_chiou@realtek.com, alsa-devel@alsa-project.org, devicetree@vger.kernel.org, Darren Hart , lgirdwood@gmail.com, linux-kernel@vger.kernel.org, Nicolin Chen , robh+dt@kernel.org, bardliao@realtek.com Message-ID: <20160811113432.GQ9347@sirena.org.uk> References: <20160728155732.GG11806@sirena.org.uk> <20160728181419.GA4742@Asurada-Nvidia> <20160728185510.GK11806@sirena.org.uk> <20160729161521.GL9681@localhost> <20160729163933.GJ10376@sirena.org.uk> <20160810170632.GL9347@sirena.org.uk> <20160810175243.GN9347@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0ZpWocbG2H/Vq+uQ" Content-Disposition: inline In-Reply-To: X-Cookie: I can't drive 55. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [alsa-devel] [PATCH] ASoC: rt5659: Add mclk controls X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --0ZpWocbG2H/Vq+uQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Aug 10, 2016 at 04:59:03PM -0500, Pierre-Louis Bossart wrote: > On 8/10/16 12:52 PM, Mark Brown wrote: > > I'm not just hinting at that, I've openly stated it quite a few times > > now! :P For the simpler CODECs it's kind of marginal if you need to > > bother but for anything more complex (even things with PLLs) it seems > > like the way forwards. > interesting, thanks for the precision. I must admit I missed this concept > completely and I didn't see any codec vendors work in this direction so far. > Ironically the x86 part may be the most straightforward... Architectures like x86 that are unable or unwilling to enable the use of the clock API are a blocker here, drivers can't make use of the API if it's not available. There are more architectures than x86 but it's the only one with any active ASoC use that I'm aware of, unfortunately the maintainers didn't react positively to attempts to enable the clock API in the past. I just sent a patch to try to fix it from the clock API side so let's hope that's a bit more helpful. --0ZpWocbG2H/Vq+uQ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXrGLHAAoJECTWi3JdVIfQyaMH/2hFq7j5i+hNtcE4lEQR6zT0 9u8fXLXH/tOMeWnu+LdjwyHwWaQRYzSiNkQaHOad30Hc/APffpWroHtmtzWWlrp3 JQwZFeHhAIWnWzkFqrbC7BEFw3YkV3gYG0SpBbphcMb6htiiHn+4+zA5Bq5jkQly 1Hba2zEngkmE2qFR9e+vltGcWgTGxo/s/fH0Rq3OizhKW/eABlkv7idsehVT20sG r1ncgoy6UtUxwensxzsNzXfTH7kd5nS2vL4nmYrqXNDybUAtWR0ROeYHkHeQ4o3l XMq6BeAnjAF0QxhRrDssU3QP/BHEaE7Osq/UhR5uyODivLWJZfRfvRlKc4mpQtk= =SgME -----END PGP SIGNATURE----- --0ZpWocbG2H/Vq+uQ--