Received: by 10.223.185.111 with SMTP id b44csp523128wrg; Fri, 9 Mar 2018 08:49:45 -0800 (PST) X-Google-Smtp-Source: AG47ELvWZTCntGYTHA1Z8l7RYF45eZBionfXZnbYsvejCuKuxzY6o4JD3Uf+mv409wsO1oVb7kfB X-Received: by 10.98.155.194 with SMTP id e63mr30428623pfk.95.1520614184965; Fri, 09 Mar 2018 08:49:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520614184; cv=none; d=google.com; s=arc-20160816; b=raUshZeQ9tt4I4asBLItoaigXzKjLF1aXVKO4hY3ZZG4a2XLTkINAuLtKFuW3E/5UF NqwRg7RpueHPIFhroSa0/kixEL7+UcwFNdLLNJDbaGsdGPiZDidFHns+X2vpI/Z8weD2 GeOHowuZhOzx3lIZpaMTg0b9RKWmXwxCh9NtvaPVSbyMiL8kyZ2W1l6gBpaQY2iWn81Q Hd+NgxSeG+ZhsYP064ORMzgBhj0zNi23HPACLgncu8zBoeOZg9cAs2bqZi0dW7yCsLTl 8yg2bRIZYPF0A1usisaChTmolyx88tC9T//zNDmTUuPX4zglzNt7grtyqYIKMEDbQ+9Q KCZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=2HRNly3OOKP3vkkqg4N248krkt73xkHta/6AQrOJnic=; b=UdVScCWhEOOb5TYmkYtzOf2FXy2WTpzkfjt7I5yTJu7KROPO0x6o04DMaidb/pFc/B 3SVeVK02jotftpEv2p8/f0JvvDpvld3O/eYcym8ujyK355wFLcAIMG6RWh3ONETyFKEL g4IPNqu6qj2P9VoGZvyBdu4Y6eAbxiRC9dA6JGQqBkjgrkoAUkPv/uSiQ3aY7V2K5+kh qAZldcZLmqCVuwHmWYq+CVVrz0iH2B01dVvG93pjt462gwVfEqarYNHLI8biZCATrIEL qD2hAE7A1kSvSH1esxYvxQUx7eFeRYLMglADkIxZFIBablvutlBXycrE2tgPxF9um64l GZEg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.co.uk Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p11si1090020pfh.247.2018.03.09.08.49.30; Fri, 09 Mar 2018 08:49:44 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.co.uk Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751246AbeCIQsk (ORCPT + 99 others); Fri, 9 Mar 2018 11:48:40 -0500 Received: from bhuna.collabora.co.uk ([46.235.227.227]:40540 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751159AbeCIQsj (ORCPT ); Fri, 9 Mar 2018 11:48:39 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: sre) with ESMTPSA id 8F6CD276FF9 Date: Fri, 9 Mar 2018 17:48:35 +0100 From: Sebastian Reichel To: Tony Lindgren Cc: Mark Brown , Lee Jones , Liam Girdwood , Rob Herring , Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@collabora.com Subject: Re: [PATCHv5 3/5] mfd: motorola-cpcap: Add audio-codec support Message-ID: <20180309164835.m442tmulhrknzqe3@earth.universe> References: <20180223200254.25685-4-sebastian.reichel@collabora.co.uk> <20180307163211.rytfli5tb47yhtug@dell> <20180308094652.qg4atjw5c3hayaz3@earth.universe> <20180308095315.mpcmx2ob6yhsnrm6@dell> <20180308102757.jyi7uo566n6nuct5@earth.universe> <20180308104831.fflq2arj5dxgntia@dell> <20180308112528.GC6019@sirena.org.uk> <20180309083414.s57eq3kw325magwz@dell> <20180309124017.GB5252@sirena.org.uk> <20180309151153.GR5799@atomide.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3cab7dvhmsquaalf" Content-Disposition: inline In-Reply-To: <20180309151153.GR5799@atomide.com> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --3cab7dvhmsquaalf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Fri, Mar 09, 2018 at 07:11:53AM -0800, Tony Lindgren wrote: > * Mark Brown [180309 12:41]: > > On Fri, Mar 09, 2018 at 08:34:14AM +0000, Lee Jones wrote: > > > On Thu, 08 Mar 2018, Mark Brown wrote: > >=20 > > > > Linux. Clocks are a big issue with audio stuff, right now sections= of > > > > the clock tree get handled in the CODEC driver but we're going to w= ant > > > > to push them out to a clock driver so we're not reimplementing hand= ling > > > > for clocks. > >=20 > > > How is the CODEC controlled? Does it have its own registers? I guess > > > by "it's not a separate device or IP" you mean that it doesn't. But > > > that begs the question, how does this then device differ from all the > > > other devices (adc, battery, charger, regulator, rtc, pwrbutton, > > > usb-phy and led)? > >=20 > > I'm not convinced that this is a particularly good idea for the other > > functions but anyway... the big thing here is that in these devices the > > CODEC is generally not the level that the IP is created at, it's a > > collection of interlinked IPs which usually includes not only audio > > stuff but also some clocking stuff. The repeatable blocks that could > > get reused independently are generally a level down from the CODEC > > level, for example if you look at something like wm8994 there's a couple > > of identical FLL IPs which could make sense to enumerate individually in > > the DT. The top level generally doesn't get reused and is purely an > > encoding of what Linux is currently doing. >=20 > It seems that most of the components in the PMICs are just standard > components packed into the PMIC with a control interface provided > over I2C or SPI. >=20 > So using compatible for things like ADC, RTC and so on makes sense > if eventually figure out which ones are shared across various > drivers. >=20 > Sounds like audio is a bit more fuzzy like Mark describes above. > And by not using a compatible for audio we can have things working > while not establishing and ABI for something that might change > in the future. I would agree, if there was no ABI now, but we still have the ABI. Instead of specifying the compatible property, we now need to specify what the node name should look like (see my binding update). That's just a different ABI. -- Sebastian --3cab7dvhmsquaalf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAlqiut4ACgkQ2O7X88g7 +ppWPw/+PciwoCoSEod5sIunUAX6qvRTE2Dn0D4xbh9/gLRXOxmNJPMabj7tXaZe KFqEMkTCmqO42klBMcQijcBTc5AC3YzMcFLI61LjlQREXeKPchn3rJhIQTwQUqQJ jXHj1Af6+pzaZohie9awDqTBdSPhnj6OGx/eG48MWPdE3oPtV4n7MWlCcj1j8e6y gyEoQfr+St08vJHPVsIzIPmC+iBXSz2dvkTiwKDMtWghKfFxuN9oAdma/4+C+idl UNzhdSgHeiTIfCBp8gHbJ9tYCSmxOUFfyTI8q2xeTs580b2B/a5kskqG9NfQ7ltc Y1bFTDCWyOb6Gyh0d243ooEZYEvQRYHAjiwkrXQQCnyfwCCsBaE7NDH9/IhMOoZf 971xNwxlz4+cDXmuRFkj2hAjQPepeyYRWCm1r+HKYaeLvIIZcQITPMczI8Tw/OyI wS7oReHF2g+H0CS8uJZKimS/kAB1vokUGm819TyfVZWY38VSu8dZ/1ZrQLf0/EUi ZJT/UqCMQ7FndZkVIqHjnKI0dKnW963QD7FpAvESrcRjl2tSeyuV1EEjMlnl/ePP R7zmp6jobKkh4JhJid6YEWzsohjh/y+ckHsKJaXhd94zwX7xNBO5OGyNDASRA/0r chjiOreAH5kNagFDs1LTmz358VoPBW3wdj6ujtGJCxqBXIFAlrU= =QYsg -----END PGP SIGNATURE----- --3cab7dvhmsquaalf--