From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753796AbcEPNNI (ORCPT ); Mon, 16 May 2016 09:13:08 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:58652 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751738AbcEPNNH (ORCPT ); Mon, 16 May 2016 09:13:07 -0400 Date: Mon, 16 May 2016 14:12:27 +0100 From: Mark Brown To: Takashi Iwai Cc: Robert Jarzmik , Haojian Zhuang , Liam Girdwood , Jaroslav Kysela , Daniel Mack , alsa-devel@alsa-project.org, linux-arm-kernel@lists.infradead.org, patches@opensource.wolfsonmicro.com, linux-kernel@vger.kernel.org Message-ID: <20160516131227.GL2953@sirena.org.uk> References: <1462050939-27940-1-git-send-email-robert.jarzmik@free.fr> <1462050939-27940-3-git-send-email-robert.jarzmik@free.fr> <87twi1hssl.fsf@belgarion.home> <87mvnrhux4.fsf@belgarion.home> <87inyeidsr.fsf@belgarion.home> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2VXyA7JGja7B50zs" Content-Disposition: inline In-Reply-To: X-Cookie: You will have a long and boring life. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 94.197.120.181 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus 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 --2VXyA7JGja7B50zs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, May 16, 2016 at 02:58:13PM +0200, Takashi Iwai wrote: > Robert Jarzmik wrote: > > Even if I'd like to not have these in bus operations, the struct snd_ac97 had a > > need for a 'caps', 'ext_id', ... fields for example. Yet these could be > > contained in the ac97_codec_device structure and not exposed to bus operations. > Do we have any example of such exceptions? For AC97, we don't need to > think of future extensions at all. I can't think of any, even for some of the more fancy CODECs used in embedded systems. --2VXyA7JGja7B50zs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXOcc5AAoJECTWi3JdVIfQ0YoH/Ao2wL7bqpBVFHhdXFpp1d6N 5gQYBRJr9vrBsAW8vn7xvhRrvFR324wDb5Y7NdCAArzOkdfTiq732qracu5sdWz2 8754/+HyS1iHA1PrC90dBc9m9YH4EqQcVikejl7RzDc+QGtsfkwOkOmbR5bh0hDP vphdnBt6VDLF4nHdMwXeaYvDljhhzNSExWtNgudXdm24ue4SrERoBR1SrXAesmte U0ewDMb4AJMxIE75tyFnvoeuU3jOQusKrc/OPfQKgmk5Vg2SIpVsYCyNGKfuMlo1 3V72Jl6DcyhkC/djU9n9+EYiDBAEw6iuMWNYwWrffULvunZdtpqveg3krD4ItnI= =tmcV -----END PGP SIGNATURE----- --2VXyA7JGja7B50zs-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@kernel.org (Mark Brown) Date: Mon, 16 May 2016 14:12:27 +0100 Subject: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus In-Reply-To: References: <1462050939-27940-1-git-send-email-robert.jarzmik@free.fr> <1462050939-27940-3-git-send-email-robert.jarzmik@free.fr> <87twi1hssl.fsf@belgarion.home> <87mvnrhux4.fsf@belgarion.home> <87inyeidsr.fsf@belgarion.home> Message-ID: <20160516131227.GL2953@sirena.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, May 16, 2016 at 02:58:13PM +0200, Takashi Iwai wrote: > Robert Jarzmik wrote: > > Even if I'd like to not have these in bus operations, the struct snd_ac97 had a > > need for a 'caps', 'ext_id', ... fields for example. Yet these could be > > contained in the ac97_codec_device structure and not exposed to bus operations. > Do we have any example of such exceptions? For AC97, we don't need to > think of future extensions at all. I can't think of any, even for some of the more fancy CODECs used in embedded systems. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: