From: Mark Brown <broonie@kernel.org>
To: Sameer Pujar <dev.spujar@gmail.com>
Cc: Sameer Pujar <spujar@nvidia.com>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
kuninori.morimoto.gx@renesas.com, lgirdwood@gmail.com,
robh+dt@kernel.org, jonathanh@nvidia.com, sharadg@nvidia.com,
thierry.reding@gmail.com, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 4/8] ASoC: tegra: Select SND_SOC_RT5659
Date: Fri, 29 Jan 2021 17:19:54 +0000 [thread overview]
Message-ID: <20210129171954.GF4560@sirena.org.uk> (raw)
In-Reply-To: <a5a8df4b-21d1-0a12-df7d-9e94c353e2b5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Fri, Jan 29, 2021 at 10:15:51PM +0530, Sameer Pujar wrote:
> On 1/29/2021 9:18 PM, Mark Brown wrote:
> > If the user wants a given CODEC driver then they should enable that
> > driver.
> Above card driver is intended to be used on multiple platforms. DT has
> already a way for user to describe the CODEC connection required for
> specific platform. So idea is enable these CODECs from driver point of view
> for this card driver and platform DT can use what is required. Also the
> CODEC driver will be a loadable module here.
No, you're missing the point of a generic driver here. This will mean
that if someone wants to build the driver into the kernel for their
embedded board they will be forced to build in every CODEC driver
someone has decided might be used with this generic driver, and even if
they're building things modular someone trying to cut down the size of
their kernel images is going to at least have to spend time building
CODEC drivers they don't want to use. Distributions should just select
all the CODEC drivers that are available in Kconfig, people configuring
for a particular target audience should be able to build only the
drivers they know they need.
> If above does not seem fine, alternatively can I just enable CODEC config
> independently from defconfig?
Yes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-29 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1611920470-24225-1-git-send-email-spujar@nvidia.com>
[not found] ` <1611920470-24225-5-git-send-email-spujar@nvidia.com>
[not found] ` <20210129124454.GB4560@sirena.org.uk>
[not found] ` <d6cb9252-246e-d6c7-7500-5f1d1823325c@nvidia.com>
[not found] ` <20210129154858.GE4560@sirena.org.uk>
2021-01-29 16:45 ` [PATCH 4/8] ASoC: tegra: Select SND_SOC_RT5659 Sameer Pujar
2021-01-29 17:19 ` Mark Brown [this message]
2021-01-29 17:28 ` Sameer Pujar
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=20210129171954.GF4560@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dev.spujar@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sharadg@nvidia.com \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.com \
/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