From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752665AbcDRPMO (ORCPT ); Mon, 18 Apr 2016 11:12:14 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:51660 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752832AbcDRPML (ORCPT ); Mon, 18 Apr 2016 11:12:11 -0400 Date: Mon, 18 Apr 2016 16:11:43 +0100 From: Mark Brown To: Peter Rosin Cc: "alsa-devel@alsa-project.org" , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , Jonathan Corbet , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "peda@lysator.liu.se" Message-ID: <20160418151143.GE3217@sirena.org.uk> References: <20160418130313.GD3217@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DHdTHwZuIuFUI+Ax" Content-Disposition: inline In-Reply-To: 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: SV: [PATCH] ASoC: docs: add clocking examples for DAI formats 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 --DHdTHwZuIuFUI+Ax Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 18, 2016 at 01:18:47PM +0000, Peter Rosin wrote: > Mark Brown wrote: > >=20 > > There aren't any (beyond the usual references to the Wolfson datasheets > > which I'd suggest should be in here) but that doesn't mean we should > > ignore this spec when we have it. > This is exactly the problem. For an outsider, it's impossible to know that > wolfson has the correct definition of the modes. Why should wolfson datas= heets > trumph nxp or ti datasheets (or whatever), if there is an inconsistency? I'm not quite sure what your concern is here? I'm saying that where there are specs we should link to them. I'm not saying we can't add to that. --DHdTHwZuIuFUI+Ax Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXFPkuAAoJECTWi3JdVIfQrJcH/jjqpVbxRjsaz5uSssXGb0nV p8RTk6gXqgF/QtZ1zOcuxj2utJ9gxfswJHQTVIKNDPyIVAw01H+r9Fuv+xpjOzc3 LlIXyDLVoM4Sb6IZxbEJazQun+t+347rQht385NfMtza9T12x8SEmE0thjwM0Saa JYfIziiadRqJ9+ZRi568eTqF7ReZv5vKLZWvepxl9qwRowI9jeJn9POw0wOIFQxx JyVIJUXKurN+x70Uh0cN4K4EIeJ+W+ubwd+udBZ9GvLfeZRXVgOaKISlUIsksQfH P4y5Yj+F7SF2sp2SQvtdNUQGKM53teGO7nZHOuyHazAKweaUU1SkKJujNhPadkE= =ZhKE -----END PGP SIGNATURE----- --DHdTHwZuIuFUI+Ax--