From: Keyon Jie <yang.jie@linux.intel.com>
To: shumingf@realtek.com, broonie@kernel.org, lgirdwood@gmail.com
Cc: oder_chiou@realtek.com, jack.yu@realtek.com,
alsa-devel@alsa-project.org, lars@metafoo.de,
albertchen@realtek.com, derek.fang@realtek.com,
sathya.prakash.m.r@intel.com, flove@realtek.com
Subject: Re: [PATCH 1/2] ASoC: rt5682: fix the random recording noise of headset
Date: Wed, 18 Mar 2020 10:31:43 +0800 [thread overview]
Message-ID: <ac2e133b-b68c-025e-cb42-8e061abf9744@linux.intel.com> (raw)
In-Reply-To: <20200317073308.11572-1-shumingf@realtek.com>
On 3/17/20 3:33 PM, shumingf@realtek.com wrote:
> From: Shuming Fan <shumingf@realtek.com>
>
> The cycle time of FIFO clock should increase 2 times to avoid
> the random recording noise issue.
> This setting could apply to all known situations in i2s mode.
Thanks for fixing this Shuming.
Just try to understand what has happened.
Can you help share more details about it, e.g.
1. the recording noise happened on headset mic or dmic?
2. will this change impact the microphone sampling clock, or the BCLK
that of the I2S bclk pin?
3. without this change, why the clk is wrong, some example?
Thanks,
~Keyon
>
> Signed-off-by: Shuming Fan <shumingf@realtek.com>
> ---
> sound/soc/codecs/rt5682.c | 2 ++
> sound/soc/codecs/rt5682.h | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/sound/soc/codecs/rt5682.c b/sound/soc/codecs/rt5682.c
> index 7ca02a5e52e9..023bc672274b 100644
> --- a/sound/soc/codecs/rt5682.c
> +++ b/sound/soc/codecs/rt5682.c
> @@ -3643,6 +3643,8 @@ static int rt5682_i2c_probe(struct i2c_client *i2c,
> RT5682_CP_CLK_HP_MASK, RT5682_CP_CLK_HP_300KHZ);
> regmap_update_bits(rt5682->regmap, RT5682_HP_CHARGE_PUMP_1,
> RT5682_PM_HP_MASK, RT5682_PM_HP_HV);
> + regmap_update_bits(rt5682->regmap, RT5682_DMIC_CTRL_1,
> + RT5682_FIFO_CLK_DIV_MASK, RT5682_FIFO_CLK_DIV_2);
>
> INIT_DELAYED_WORK(&rt5682->jack_detect_work,
> rt5682_jack_detect_handler);
> diff --git a/sound/soc/codecs/rt5682.h b/sound/soc/codecs/rt5682.h
> index 43de6e802309..0baeece84ec4 100644
> --- a/sound/soc/codecs/rt5682.h
> +++ b/sound/soc/codecs/rt5682.h
> @@ -657,6 +657,8 @@
> #define RT5682_DMIC_1_EN_SFT 15
> #define RT5682_DMIC_1_DIS (0x0 << 15)
> #define RT5682_DMIC_1_EN (0x1 << 15)
> +#define RT5682_FIFO_CLK_DIV_MASK (0x7 << 12)
> +#define RT5682_FIFO_CLK_DIV_2 (0x1 << 12)
> #define RT5682_DMIC_1_DP_MASK (0x3 << 4)
> #define RT5682_DMIC_1_DP_SFT 4
> #define RT5682_DMIC_1_DP_GPIO2 (0x0 << 4)
>
next prev parent reply other threads:[~2020-03-18 2:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 7:33 [PATCH 1/2] ASoC: rt5682: fix the random recording noise of headset shumingf
2020-03-18 2:31 ` Keyon Jie [this message]
2020-03-18 3:06 ` Albert Chen
2020-03-18 3:31 ` Keyon Jie
2020-03-18 6:07 ` Albert Chen
2020-03-18 9:36 ` Keyon Jie
2020-03-18 18:51 ` Applied "ASoC: rt5682: fix the random recording noise of headset" to the asoc tree 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=ac2e133b-b68c-025e-cb42-8e061abf9744@linux.intel.com \
--to=yang.jie@linux.intel.com \
--cc=albertchen@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=sathya.prakash.m.r@intel.com \
--cc=shumingf@realtek.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