From: Takashi Iwai <tiwai@suse.de>
To: Jie Yang <yang.jie@intel.com>
Cc: broonie@kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, liam.r.girdwood@intel.com,
vivian.zhang@intel.com
Subject: Re: [PATCH v3 1/2] ALSA: Kconfig: add config item SND_PROC_FS for expert
Date: Wed, 27 May 2015 11:55:39 +0200 [thread overview]
Message-ID: <s5hd21mbazo.wl-tiwai@suse.de> (raw)
In-Reply-To: <1432717818-4685-2-git-send-email-yang.jie@intel.com>
At Wed, 27 May 2015 17:10:17 +0800,
Jie Yang wrote:
>
> For some embedded devices, we need reduce code size and data
> footprint as much as possible, e.g. disabling procfs, hw/sw
> params refinement, mmap, dpcm, dapm, compressed API...
>
> Here add SND_PROC_FS item for expert, we can unselect it to
> disable sound proc FS and reduce memory footprint.
>
> Signed-off-by: Jie Yang <yang.jie@intel.com>
> ---
> sound/core/Kconfig | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/sound/core/Kconfig b/sound/core/Kconfig
> index 63cc2e9..4542554 100644
> --- a/sound/core/Kconfig
> +++ b/sound/core/Kconfig
> @@ -225,4 +225,13 @@ config SND_DMA_SGBUF
> def_bool y
> depends on X86
>
> +config SND_PROC_FS
> + bool "Sound Proc FS Support" if EXPERT
> + depends on PROC_FS
> + default y
> + help
> + Say 'N' to disable Sound proc FS, which may reduce code size about
> + 9KB on x86_64 platform.
> + If unsure say Y.
> +
> source "sound/core/seq/Kconfig"
There is SND_VERBOSE_PROCFS that also depends on PROC_FS.
You should change it as well to depend on SND_PROC_FS.
Takashi
next prev parent reply other threads:[~2015-05-27 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 9:10 [PATCH v3 0/2] reducing memory footprint of ALSA Jie Yang
2015-05-27 9:10 ` [PATCH v3 1/2] ALSA: Kconfig: add config item SND_PROC_FS for expert Jie Yang
2015-05-27 9:55 ` Takashi Iwai [this message]
2015-05-27 11:10 ` Jie, Yang
2015-05-27 9:10 ` [PATCH v3 2/2] ALSA: replace CONFIG_PROC_FS with CONFIG_SND_PROC_FS Jie Yang
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=s5hd21mbazo.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vivian.zhang@intel.com \
--cc=yang.jie@intel.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