From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1757223AbdDRRPh (ORCPT <rfc822;w@1wt.eu>);
        Tue, 18 Apr 2017 13:15:37 -0400
Received: from mezzanine.sirena.org.uk ([106.187.55.193]:56128 "EHLO
        mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753855AbdDRRPf (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 18 Apr 2017 13:15:35 -0400
Date: Tue, 18 Apr 2017 18:15:19 +0100
From: Mark Brown <broonie@kernel.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
        Jose Abreu <Jose.Abreu@synopsys.com>, Arnd Bergmann <arnd@arndb.de>
Message-ID: <20170418171519.csiftftd434psyn5@sirena.org.uk>
References: <20170418105954.23368-1-lkundrak@v3.sk>
 <20170418151834.c7e5fivmgn73sbwd@sirena.org.uk>
 <1492532010.28092.12.camel@v3.sk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="dk3hqasakxi55qak"
Content-Disposition: inline
In-Reply-To: <1492532010.28092.12.camel@v3.sk>
X-Cookie: User hostile.
User-Agent: NeoMutt/20170306 (1.8.0)
X-SA-Exim-Connect-IP: 2001:470:1f1d:6b5::3
X-SA-Exim-Mail-From: broonie@sirena.org.uk
Subject: Re: [PATCH] ASoC: dwc: disallow building designware_pcm as a module
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


--dk3hqasakxi55qak
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Apr 18, 2017 at 06:13:30PM +0200, Lubomir Rintel wrote:

> I don't think designware_pcm is a separate driver. It looks tightly
> coupled with designware_i2s: you can either disable designware_pcm
> altogether at build time or always load it together with
> designware_i2s.

Yes, they're closely coupled but we might still want them both as a
module.

--dk3hqasakxi55qak
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlj2SaYACgkQJNaLcl1U
h9BF5Qf/csQ3YSCJ7J56qZYYPSdpokbmobpYSw25qmGdIALSfxwvVKeKQCiouE54
VZN7nZwX7IjcWLnutLRNxIe8+PTtbH+H1gV6Lu14TpZbb3OzTdbx7LKJpUMbL1RF
mx665O3omLzPES7JhfNQayQJbCDr1cbRVWOA95SqqnSCTpxQKL3K3QmzifmHpa1r
IbaixHet/C2JjDQDVWPENFGy7Pn2VfXuzlXkVOfrzssIJFTNDzGDkHNdUMxRfzVq
U24fdgKyTLTxz/9R2fXC7b1bm+zYJ9/Pm+riwHHShr8NTUalNTJRdomvFjDT81BE
7d4JPcXFXqvvg9ZiR16yQ5/NxM3KCA==
=YXGw
-----END PGP SIGNATURE-----

--dk3hqasakxi55qak--