From: Daniel Mack <zonque@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: [PATCH] ALSA: ASoC: add codec driver for TI TAS5086
Date: Fri, 08 Mar 2013 13:26:35 +0100 [thread overview]
Message-ID: <5139D8FB.4070500@gmail.com> (raw)
In-Reply-To: <20130308114251.GF28481@opensource.wolfsonmicro.com>
Hi Mark,
thanks for your quick review.
On 08.03.2013 12:42, Mark Brown wrote:
> On Fri, Mar 08, 2013 at 12:07:13PM +0100, Daniel Mack wrote:
>> +static int tas5086_digital_mute(struct snd_soc_dai *dai, int mute)
>> +{
>> + struct snd_soc_codec *codec = dai->codec;
>> + struct tas5086_private *priv = snd_soc_codec_get_drvdata(codec);
>> +
>> + return regmap_write(priv->regmap, TAS5086_SOFT_MUTE,
>> + mute ? 0x3f : 0x00);
>
> Please avoid the ternery operator. It'd be nice to switch over to
> mute_stream() too.
I wasn't aware of steam_mute. How's that supposed to be used? I'm asking
because when using 4-channel playback, the driver gets this callback for
stream == 0 only. Am I supposed to (un)mute all channels here,
regardless of the stream parameter passed in?
>> +#ifdef CONFIG_PM
>> +static int tas5086_soc_suspend(struct snd_soc_codec *codec)
>> +{
>> + return 0;
>> +}
>
> Empty functions can just be omitted, though it might make sense to hold
> the device in reset over suspend.
I can't test this at the moment, so I'll skip suspend functionality
support for now. Will send another follow-up patch in the future for this.
Thanks,
Daniel
next prev parent reply other threads:[~2013-03-08 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 11:07 [PATCH] ALSA: ASoC: add codec driver for TI TAS5086 Daniel Mack
2013-03-08 11:42 ` Mark Brown
2013-03-08 12:26 ` Daniel Mack [this message]
2013-03-08 12:30 ` Mark Brown
2013-03-08 12:31 ` Daniel Mack
2013-05-22 17:50 ` jonsmirl
2013-05-22 17:55 ` Daniel Mack
2013-05-22 18:01 ` jonsmirl
2013-05-22 18:20 ` jonsmirl
2013-05-22 18:24 ` jonsmirl
2013-05-22 18:25 ` Daniel Mack
2013-05-22 18:33 ` jonsmirl
2013-05-22 18:36 ` Daniel Mack
2013-05-22 19:31 ` Mark Brown
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=5139D8FB.4070500@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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;
as well as URLs for NNTP newsgroup(s).