Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751947AbcDRJxg (ORCPT ); Mon, 18 Apr 2016 05:53:36 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:50844 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751497AbcDRJxf (ORCPT ); Mon, 18 Apr 2016 05:53:35 -0400 Date: Mon, 18 Apr 2016 10:53:02 +0100 From: Mark Brown To: Xing Zheng Cc: linux-rockchip@lists.infradead.org, heiko@sntech.de, Adam.Thomson@diasemi.com, sugar.zhang@rock-chips.com, jay.xu@rock-chips.com, Liam Girdwood , Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Message-ID: <20160418095302.GN3217@sirena.org.uk> References: <1460967452-24574-1-git-send-email-zhengxing@rock-chips.com> <1460967452-24574-2-git-send-email-zhengxing@rock-chips.com> <20160418092218.GL3217@sirena.org.uk> <5714AC57.2070901@rock-chips.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fpolVoprVozDR81Y" Content-Disposition: inline In-Reply-To: <5714AC57.2070901@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 1/3] ASoC: jack: Add a jack detect callback 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: 1013 Lines: 32 --fpolVoprVozDR81Y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Apr 18, 2016 at 05:43:51PM +0800, Xing Zheng wrote: > The patch_1/3 add an export of a function that calls the _detect_jack_ > function > when a codec supports jack detection and fill the _detect_jack_ function in > the > struct snd_soc_codec_driver. But why would anything ever call this function? How is this supposed to be used? --fpolVoprVozDR81Y Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXFK59AAoJECTWi3JdVIfQoIkH/11rNOsK3IY82eHAhlPRvn4c qZPm1puFWdfye0GlLf/hkzuXAj2yX/IDiUoOsKo8tqG3hl01+34dMLrpbwK2yzJV OOW//DGzsBAhg4aDWJ9XYs5cF7eHDcici/mwavcUASJ4AaxyxcPAIelGMub52E35 AAJiseqfVg+tGbkRjfwNA+jJJ3TrzZ+jwbgjGVYDlXM1IIt6dPcaxFjzd+nsoSuf Qn3ZqvAf2/YYHIZL30ih0WDQx6fC+kngRdrZe6TB1I06exLAtXwdwQ3X3+NUtejf HsX1rHKU4TChVb9X3J0msPlDh09ykK+U1pQqTqlIryW3wUOrk/u8WkdWp02f4Vw= =KI4t -----END PGP SIGNATURE----- --fpolVoprVozDR81Y--