From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Jose Abreu <Jose.Abreu@synopsys.com>,
Lubomir Rintel <lkundrak@v3.sk>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] ASoC: dwc: disallow building designware_pcm as a module
Date: Thu, 20 Apr 2017 22:24:14 +0200 [thread overview]
Message-ID: <s5h37d2su8h.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170420194646.qcpu7w3acjyfmeu5@sirena.org.uk>
On Thu, 20 Apr 2017 21:46:46 +0200,
Mark Brown wrote:
>
> On Wed, Apr 19, 2017 at 05:48:15PM +0100, Jose Abreu wrote:
>
> > What do you think Mark? If you want to keep the PCM as a module
> > then we will need to abstract this more, by reducing the
> > dependencies.
>
> I think forcing this to be built in to the kernel (which is what the
> commit message says the change is going to do) is an obviously bad
> idea. Anything we add to the base kernel image needs to have a good
> reason to be there and it is hard to think what that reason might be for
> any audio driver, we need to be able to put this code into a module.
Well, I guess the original patch description caused a big confusion.
As far as I see, the intention of the patch is not about the module or
built-in kernel. Instead it's rather to fold designware_pcm stuff
into the single designware_i2s driver.
The former is merely an extension of the latter driver, and the latter
invokes the former directly. Thus there is little merit to keep them
separate. I think the current code is even buggy, which allows to
leave CONFIG_SND_DESIGNWARE_I2S=y and CONFIG_SND_DESIGNWARE_PCM=m.
So, I think Lubomir's change is right. But the patch subject and
description should be rephrased.
One thing I don't like is the rename of the file. But in this
particular case, it's unavoidable unless we rename the module name.
BTW, we should drop the superfluous EXPORT_SYMBOL*(), too.
thanks,
Takashi
next prev parent reply other threads:[~2017-04-20 20:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 10:59 [PATCH] ASoC: dwc: disallow building designware_pcm as a module Lubomir Rintel
2017-04-18 15:18 ` Mark Brown
2017-04-18 16:13 ` Lubomir Rintel
2017-04-18 17:15 ` Mark Brown
2017-04-19 16:12 ` Jose Abreu
2017-04-19 16:14 ` Lubomir Rintel
2017-04-19 16:48 ` Jose Abreu
2017-04-20 19:46 ` Mark Brown
2017-04-20 20:24 ` Takashi Iwai [this message]
2017-04-20 20:25 ` Mark Brown
2017-04-21 10:34 ` Jose Abreu
2017-04-21 10:39 ` Takashi Iwai
2017-04-21 10:49 ` [alsa-devel] " Mark Brown
2017-04-27 18:49 ` Jose Abreu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5h37d2su8h.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Jose.Abreu@synopsys.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).