Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753744AbcDVJYE (ORCPT ); Fri, 22 Apr 2016 05:24:04 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:33832 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554AbcDVJYB (ORCPT ); Fri, 22 Apr 2016 05:24:01 -0400 Date: Fri, 22 Apr 2016 10:22:50 +0100 From: Mark Brown To: Xing Zheng Cc: Rob Herring , linux-rockchip@lists.infradead.org, heiko@sntech.de, Adam.Thomson@diasemi.com, sugar.zhang@rock-chips.com, jay.xu@rock-chips.com, Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , Arnaud Pouliquen , Aaro Koskinen , Andrew Lunn , Mengdong Lin , Jun Nie , Jyri Sarha , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org Message-ID: <20160422092250.GA3217@sirena.org.uk> References: <1460967452-24574-1-git-send-email-zhengxing@rock-chips.com> <1460967452-24574-3-git-send-email-zhengxing@rock-chips.com> <20160421141921.GA25900@rob-hp-laptop> <57197BBA.50304@rock-chips.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TWLMYU3k2ba4mEMM" Content-Disposition: inline In-Reply-To: <57197BBA.50304@rock-chips.com> X-Cookie: Tomorrow, you can be anywhere. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 2/3] ASoC: simple-card: Add support jack detection via codec X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1068 Lines: 31 --TWLMYU3k2ba4mEMM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Apr 22, 2016 at 09:17:46AM +0800, Xing Zheng wrote: > Hi Mark, the other question here, how do we make sense to use the > simple-card to call the "snd_soc_dai_set_pll" if the codec (like da7219) > requires do this? What we should do there is move the CODEC clocking to be represented using the clock API and then there are common clock bindings that already exist for configuring clocks. --TWLMYU3k2ba4mEMM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXGe1pAAoJECTWi3JdVIfQ8VEH/R6U0WQdP79xYu08En2ZZeG+ KxEwOe3xjOB9qkzifp9ONKasWkmYQBiWJuTty9rNUI5zxuXyY5rrUVaeLNXhxmgV uRzZ2Df0rZHdmrwTev1+fe6GKu21c1o1St5ZxhW2roWBtL3U78z2pWL+/M66YW/2 em0hVwD7Nuxf+8L+B1xU5JDwIkgLFBOo80A95sfpUJLKfBRIwywXBOoA2Uqpk7tM IsRCs+Rnw8KOuDT+qplYF2ZMt+/V42JeO0RvL3hdKdnpL5YeX8uSEAMWgBI2hUAN qVirdIV8/BCv360vcIgp033tGJzkusZgM027YTGU2NNjFDp/XdzSCwNDyGW6AiM= =cGoo -----END PGP SIGNATURE----- --TWLMYU3k2ba4mEMM--