From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933797AbcHJV7V (ORCPT ); Wed, 10 Aug 2016 17:59:21 -0400 Received: from mga03.intel.com ([134.134.136.65]:61216 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751070AbcHJV7T (ORCPT ); Wed, 10 Aug 2016 17:59:19 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,502,1464678000"; d="scan'208";a="863320348" Subject: Re: [alsa-devel] [PATCH] ASoC: rt5659: Add mclk controls To: Mark Brown References: <1469660568-3511-1-git-send-email-nicoleotsuka@gmail.com> <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> 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 From: Pierre-Louis Bossart Message-ID: Date: Wed, 10 Aug 2016 16:59:03 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160810175243.GN9347@sirena.org.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/10/16 12:52 PM, Mark Brown wrote: > On Wed, Aug 10, 2016 at 12:31:28PM -0500, Pierre-Louis Bossart wrote: > >> If we want to be consistent then we need to have a framework that handles >> both the SOC clock sources and the codec internal clock tree (including >> dividers and switches) >> I wonder if what you are hinting at is the codec driver modeling its >> internal PLL/clock tree with the clock API? > > 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...