linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: OMAP2+: omap2plus_defconfig: enable twl4030 SoC audio
Date: Tue, 27 Nov 2012 10:58:10 +0100	[thread overview]
Message-ID: <50B48EB2.1040804@ti.com> (raw)
In-Reply-To: <1353979275-6237-1-git-send-email-javier.martinez@collabora.co.uk>

On 11/27/2012 02:21 AM, Javier Martinez Canillas wrote:
> Many TI OMAP SoC based boards that uses twl4030 as codec have
> been updated to use the unified audio driver (omap-twl4030)
> since they have similar audio setup.
> 
> So, is good to have it built to add audio support to these boards.
> 
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>

I also agree that it is a good practice to enable this in the defconfig.

Acked-by: Peter Ujfalusi <peter.ujfalusi@ti.com>

> ---
>  arch/arm/configs/omap2plus_defconfig |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/configs/omap2plus_defconfig b/arch/arm/configs/omap2plus_defconfig
> index 7c6cbdf..022212c 100644
> --- a/arch/arm/configs/omap2plus_defconfig
> +++ b/arch/arm/configs/omap2plus_defconfig
> @@ -172,6 +172,7 @@ CONFIG_SND_DEBUG=y
>  CONFIG_SND_USB_AUDIO=m
>  CONFIG_SND_SOC=m
>  CONFIG_SND_OMAP_SOC=m
> +CONFIG_SND_OMAP_SOC_OMAP_TWL4030=m
>  CONFIG_SND_OMAP_SOC_OMAP3_PANDORA=m
>  CONFIG_USB=y
>  CONFIG_USB_DEBUG=y
> 


-- 
P?ter

  reply	other threads:[~2012-11-27  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  1:21 [PATCH 1/1] ARM: OMAP2+: omap2plus_defconfig: enable twl4030 SoC audio Javier Martinez Canillas
2012-11-27  9:58 ` Peter Ujfalusi [this message]
2012-12-13 23:58   ` Javier Martinez Canillas
2012-12-14  0:02     ` Tony Lindgren

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=50B48EB2.1040804@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).