From: Andrew Lunn <andrew@lunn.ch>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
alsa-devel@alsa-project.org, Xiubo Li <Li.Xiubo@freescale.com>,
Liam Girdwood <lgirdwood@gmail.com>, Jyri Sarha <jsarha@ti.com>,
Mark Brown <broonie@kernel.org>,
Jean Delvare <khali@linux-fr.org>
Subject: Re: Using simple-card to replace kirkwood-t5325.c
Date: Wed, 16 Apr 2014 13:13:33 +0200 [thread overview]
Message-ID: <20140416111333.GA11310@lunn.ch> (raw)
In-Reply-To: <534D7D31.6040802@metafoo.de>
On Tue, Apr 15, 2014 at 08:40:49PM +0200, Lars-Peter Clausen wrote:
> On 04/15/2014 06:13 PM, Andrew Lunn wrote:
> >Hi Folks
>
> Adding a few people to Cc.
>
> >
> >I'm an ALSA newbie, so if i say anything stupid, please let me know.
> >
> >I'm trying to replace sound/soc/kirkwood/kirkwood-t5325.c with DT,
> >using simple-card. I can get near, but i'm missing two things:
> >
> >There does not appear to be a way to represent this in DT:
> >
> >static int t5325_dai_init(struct snd_soc_pcm_runtime *rtd)
> >{
> > struct snd_soc_codec *codec = rtd->codec;
> > struct snd_soc_dapm_context *dapm = &codec->dapm;
> >
> > snd_soc_dapm_enable_pin(dapm, "Mic Jack");
> > snd_soc_dapm_enable_pin(dapm, "Headphone Jack");
> > snd_soc_dapm_enable_pin(dapm, "Speaker");
> >
> > return 0;
> >}
> >
> >It appears that quite a few drivers need to enable pins.
>
> I'm not sure where this got started, but this mostly seems to be
> cargo-culting. External pins are enabled by default, there is no
> need to call snd_soc_dapm_enable_pin() unless
> snd_soc_dapm_disable_pin() has been called before for the same pin.
Ah, thanks for saying this. I just tested without, and all is good.
Thanks
Andrew
prev parent reply other threads:[~2014-04-16 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 16:13 Using simple-card to replace kirkwood-t5325.c Andrew Lunn
2014-04-15 18:40 ` Lars-Peter Clausen
2014-04-15 22:29 ` Mark Brown
2014-04-16 11:17 ` Andrew Lunn
2014-04-16 11:13 ` Andrew Lunn [this message]
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=20140416111333.GA11310@lunn.ch \
--to=andrew@lunn.ch \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jsarha@ti.com \
--cc=khali@linux-fr.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@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