From: Mark Brown <broonie@kernel.org>
To: Ryan Lee <ryans.lee@maximintegrated.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
kuninori.morimoto.gx@renesas.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, ryan.lee.maxim@gmail.com
Subject: Re: [PATCH 1/3] ASoC: max98927: Added support for DSP_A and DSP_B format
Date: Thu, 14 Sep 2017 11:49:49 -0700 [thread overview]
Message-ID: <20170914184949.enuziddz27polfyf@sirena.org.uk> (raw)
In-Reply-To: <1505146339-19380-1-git-send-email-ryans.lee@maximintegrated.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Mon, Sep 11, 2017 at 09:12:18AM -0700, Ryan Lee wrote:
> Signed-off-by: Ryan Lee <ryans.lee@maximintegrated.com>
> ---
Please make an effort to write changelogs that clearly describe the
change you're making. This is doing way more than just implementing DSP
mode, it's also adding a fairly complicated set_tdm_slot() implementation
which isn't mentioned at all. It probably needs splitting into multiple
patches as well.
> @@ -414,6 +504,9 @@ static int max98927_dac_event(struct snd_soc_dapm_widget *w,
> struct max98927_priv *max98927 = snd_soc_codec_get_drvdata(codec);
>
> switch (event) {
> + case SND_SOC_DAPM_PRE_PMU:
> + max98927->tdm_mode = 0;
> + break;
> case SND_SOC_DAPM_POST_PMU:
> regmap_update_bits(max98927->regmap,
> MAX98927_R003A_AMP_EN,
Why is an event associated with the DAC changing something related to
the DAI format? These things should be unrelated.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-09-14 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 16:12 Ryan Lee
2017-09-11 16:12 ` [PATCH 2/3] ASoC: max98927: Added controls for Envelope tracking Ryan Lee
2017-09-14 18:49 ` Mark Brown [this message]
2017-09-15 0:30 ` [PATCH 1/3] ASoC: max98927: Added support for DSP_A and DSP_B format Ryan Lee
-- strict thread matches above, loose matches on Subject: below --
2017-09-01 21:35 Ryan Lee
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=20170914184949.enuziddz27polfyf@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=ryan.lee.maxim@gmail.com \
--cc=ryans.lee@maximintegrated.com \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®