From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Turquette Subject: Re: [PATCH v5 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver Date: Mon, 19 Aug 2013 17:06:25 -0700 Message-ID: <20130820000625.4443.23018@quantum> References: <2805432.jMVhHxhr1m@flatron> <20130817145316.GT26614@pengutronix.de> <8770601.066pCcRnTh@flatron> <20130819093543.GF3719@e106331-lin.cambridge.arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by alsa0.perex.cz (Postfix) with ESMTP id 98830265136 for ; Tue, 20 Aug 2013 02:06:33 +0200 (CEST) Received: by mail-pd0-f169.google.com with SMTP id r10so5918069pdi.14 for ; Mon, 19 Aug 2013 17:06:32 -0700 (PDT) In-Reply-To: <20130819093543.GF3719@e106331-lin.cambridge.arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Mark Rutland , Tomasz Figa Cc: "devicetree@vger.kernel.org" , "alsa-devel@alsa-project.org" , "lars@metafoo.de" , "ian.campbell@citrix.com" , Pawel Moll , "swarren@wwwdotorg.org" , "festevam@gmail.com" , Sascha Hauer , Nicolin Chen , "timur@tabi.org" , "rob.herring@calxeda.com" , "broonie@kernel.org" , "p.zabel@pengutronix.de" , "galak@codeaurora.org" , "shawn.guo@linaro.org" , "linuxppc-dev@lists.ozlabs.org" List-Id: alsa-devel@alsa-project.org Quoting Mark Rutland (2013-08-19 02:35:43) > On Sat, Aug 17, 2013 at 04:17:18PM +0100, Tomasz Figa wrote: > > On Saturday 17 of August 2013 16:53:16 Sascha Hauer wrote: > > > On Sat, Aug 17, 2013 at 02:28:04PM +0200, Tomasz Figa wrote: > > > > > > > Also I would make this option required. Use a dummy clock for > > > > > > > mux > > > > > > > inputs that are grounded for a specific SoC. > > > > > > > > > > > > Some clocks are not from CCM and we haven't defined in > > > > > > imx6q-clk.txt, > > > > > > so in most cases we can't provide a phandle for them, eg: > > > > > > spdif_ext. > > > > > > I think it's a bit hard to force it to be 'required'. An > > > > > > 'optional' > > > > > > looks more flexible to me and a default one is ensured even if > > > > > > it's > > > > > > missing. > > > > > > > > > > <&clks 0> is the dummy clock. This can be used for all input clocks > > > > > not > > > > > defined by the SoC. > > > > > > > > Where does this assumption come from? Is it documented anywhere? > > > > > > This is how all i.MX clock bindings currently are. See > > > Documentation/devicetree/bindings/clock/imx*-clock.txt > > > > OK, thanks. > > > > I guess we need some discussion on dummy clocks vs skipped clocks. I think > > we want some consistency on this, don't we? > > > > If we really need a dummy clock, then we might also want a generic way to > > specify it. > > What do we actually mean by a "dummy clock"? We already have bindings > for "fixed-clock" and co friends describe relatively simple > preconfigured clocks. Some platforms have a fake clock which defines noops callbacks and basically doesn't do anything. This is analogous to the dummy regulator implementation. A central one could be registered by the clock core, as is done by the regulator core. I'll add this to the todo list. Regards, Mike > > If a clock isn't actually wired, we shouldn't describe it at all, or > we're describing what Linux wants to think rather than what the hardware > actually is. That can easily be handled with clock-names. > > Thanks, > Mark.