From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755615AbbIWQgB (ORCPT ); Wed, 23 Sep 2015 12:36:01 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:47330 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752728AbbIWQgA (ORCPT ); Wed, 23 Sep 2015 12:36:00 -0400 Date: Wed, 23 Sep 2015 09:20:26 -0700 From: Mark Brown To: Sugar Zhang Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com, heiko@sntech.de, alsa-devel@alsa-project.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Message-ID: <20150923162026.GP30445@sirena.org.uk> References: <1442979683-9441-1-git-send-email-sugar.zhang@rock-chips.com> <1442979683-9441-3-git-send-email-sugar.zhang@rock-chips.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jZ6LB7VX2Q2qroxd" Content-Disposition: inline In-Reply-To: <1442979683-9441-3-git-send-email-sugar.zhang@rock-chips.com> X-Cookie: NOBODY EXPECTS THE SPANISH INQUISITION! User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 70.35.39.2 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 2/2] Documentation: DT bindings: rockchip-i2s: add capture and lrck-mode 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 --jZ6LB7VX2Q2qroxd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Sep 23, 2015 at 11:41:23AM +0800, Sugar Zhang wrote: > rockchip,lrck-mode: 0: rxtx separate, 1: tx share, 2: rx share. > default use 'rxtx separate' mode. I'm slightly confused about this property - is this covering differences in the IP deployed on different SoCs or is it covering how the SoC is wired into the board? If it's for how the SoC is wired into the board (ie, Rx and Tx wired together) then this should already be covered by either the machine driver or the device at the other end of the link. --jZ6LB7VX2Q2qroxd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWAtFKAAoJECTWi3JdVIfQDQ8H/R2lx+HhPy7PD62lJRDGDLRS XIM8iOiAieazMDQCkLRhYOHMpVLsEfSSSRCmGdGG1q5HWhFn5p8KjQWDG13hYCmx 9YwRTfk52+2i/EnzpKHdssGz7pzisk3SB+WOuUKPPo5Z6672T8jwtssDeC960AI7 JepwtX63AXbGLKm8goE+Ilx3l0FivrdfXPF53hSXduBSoGEr0Yvzdh4iN1QHh2t5 K4XxU9OrvUf1WOvpOv8V1+7Oq19x5bQA+n2mo+Vr0kwdoOwLsg7jlnpJwUwk3ApW OEcQ0IIvp03bwccCLf6YtwrILZ11Zjoq5EWahzy94wqLPWYJTEHso/jk+KM9eqY= =JdgA -----END PGP SIGNATURE----- --jZ6LB7VX2Q2qroxd--