* [PATCH] ASoC: rt5670: patch reg-0x8a
@ 2016-06-17 4:08 Bard Liao
2016-06-17 11:10 ` Mark Brown
2016-06-21 18:52 ` Applied "ASoC: rt5670: patch reg-0x8a" to the asoc tree Mark Brown
0 siblings, 2 replies; 4+ messages in thread
From: Bard Liao @ 2016-06-17 4:08 UTC (permalink / raw)
To: broonie, lgirdwood
Cc: oder_chiou, jack.yu, alsa-devel, lars, Bard Liao, flove
reg-8a assign the tracking source for each ASRC tracker. The default
value is 0x0000 which means all ASRC trackers will track LRCK1. But
in most case, we wish each ASRC tracker track the corresponding LRCK.
i.e. ASRC1 tracks LRCK1, ASRC2 tracks LRCK2 and so on. So, we rewrite
reg-8a as 0x0123.
Signed-off-by: Bard Liao <bardliao@realtek.com>
---
sound/soc/codecs/rt5670.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/rt5670.c b/sound/soc/codecs/rt5670.c
index 0af5ddb..8ef467f 100644
--- a/sound/soc/codecs/rt5670.c
+++ b/sound/soc/codecs/rt5670.c
@@ -55,6 +55,7 @@ static const struct reg_sequence init_list[] = {
{ RT5670_PR_BASE + 0x14, 0x9a8a },
{ RT5670_PR_BASE + 0x38, 0x3ba1 },
{ RT5670_PR_BASE + 0x3d, 0x3640 },
+ { 0x8a, 0x0123 },
};
static const struct reg_default rt5670_reg[] = {
@@ -131,7 +132,7 @@ static const struct reg_default rt5670_reg[] = {
{ 0x87, 0x0000 },
{ 0x88, 0x0000 },
{ 0x89, 0x0000 },
- { 0x8a, 0x0000 },
+ { 0x8a, 0x0123 },
{ 0x8b, 0x0000 },
{ 0x8c, 0x0003 },
{ 0x8d, 0x0000 },
--
1.8.1.1.439.g50a6b54
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] ASoC: rt5670: patch reg-0x8a
2016-06-17 4:08 [PATCH] ASoC: rt5670: patch reg-0x8a Bard Liao
@ 2016-06-17 11:10 ` Mark Brown
2016-06-20 2:10 ` Bard Liao
2016-06-21 18:52 ` Applied "ASoC: rt5670: patch reg-0x8a" to the asoc tree Mark Brown
1 sibling, 1 reply; 4+ messages in thread
From: Mark Brown @ 2016-06-17 11:10 UTC (permalink / raw)
To: Bard Liao; +Cc: oder_chiou, jack.yu, alsa-devel, lars, lgirdwood, flove
[-- Attachment #1.1: Type: text/plain, Size: 398 bytes --]
On Fri, Jun 17, 2016 at 12:08:02PM +0800, Bard Liao wrote:
> reg-8a assign the tracking source for each ASRC tracker. The default
> value is 0x0000 which means all ASRC trackers will track LRCK1. But
> in most case, we wish each ASRC tracker track the corresponding LRCK.
> i.e. ASRC1 tracks LRCK1, ASRC2 tracks LRCK2 and so on. So, we rewrite
> reg-8a as 0x0123.
Shouldn't this be configurable?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] ASoC: rt5670: patch reg-0x8a
2016-06-17 11:10 ` Mark Brown
@ 2016-06-20 2:10 ` Bard Liao
0 siblings, 0 replies; 4+ messages in thread
From: Bard Liao @ 2016-06-20 2:10 UTC (permalink / raw)
To: Mark Brown
Cc: Oder Chiou, Jack Yu, alsa-devel@alsa-project.org, lars@metafoo.de,
lgirdwood@gmail.com, Flove
> -----Original Message-----
> From: Mark Brown [mailto:broonie@kernel.org]
> Sent: Friday, June 17, 2016 7:10 PM
> To: Bard Liao
> Cc: lgirdwood@gmail.com; alsa-devel@alsa-project.org;
> lars@metafoo.de; Flove; Oder Chiou; Jack Yu
> Subject: Re: [PATCH] ASoC: rt5670: patch reg-0x8a
>
> On Fri, Jun 17, 2016 at 12:08:02PM +0800, Bard Liao wrote:
>
> > reg-8a assign the tracking source for each ASRC tracker. The default
> > value is 0x0000 which means all ASRC trackers will track LRCK1. But in
> > most case, we wish each ASRC tracker track the corresponding LRCK.
> > i.e. ASRC1 tracks LRCK1, ASRC2 tracks LRCK2 and so on. So, we rewrite
> > reg-8a as 0x0123.
>
> Shouldn't this be configurable?
In hardware of view, yes. But, it is not necessary since we can choose
which ASRC we want to use. That is selected by another register and is
implemented by rt5670_sel_asrc_clk_src function. Without this patch,
no matter what ASRC is selected, it will track LRCK1. But with this patch,
we can use ASRC2 to track LRCK2. It means we can decide which LRCK
is tracked by selecting which ASRC we are using with a fixed value of
reg-8a.
>
> ------Please consider the environment before printing this e-mail.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Applied "ASoC: rt5670: patch reg-0x8a" to the asoc tree
2016-06-17 4:08 [PATCH] ASoC: rt5670: patch reg-0x8a Bard Liao
2016-06-17 11:10 ` Mark Brown
@ 2016-06-21 18:52 ` Mark Brown
1 sibling, 0 replies; 4+ messages in thread
From: Mark Brown @ 2016-06-21 18:52 UTC (permalink / raw)
To: Bard Liao
Cc: oder_chiou, jack.yu, alsa-devel, lars, lgirdwood, broonie, flove
The patch
ASoC: rt5670: patch reg-0x8a
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
>From 874352a763ba2df55093d2651158be40999e9cbe Mon Sep 17 00:00:00 2001
From: Bard Liao <bardliao@realtek.com>
Date: Fri, 17 Jun 2016 12:08:02 +0800
Subject: [PATCH] ASoC: rt5670: patch reg-0x8a
reg-8a assign the tracking source for each ASRC tracker. The default
value is 0x0000 which means all ASRC trackers will track LRCK1. But
in most case, we wish each ASRC tracker track the corresponding LRCK.
i.e. ASRC1 tracks LRCK1, ASRC2 tracks LRCK2 and so on. So, we rewrite
reg-8a as 0x0123.
Signed-off-by: Bard Liao <bardliao@realtek.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
sound/soc/codecs/rt5670.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/rt5670.c b/sound/soc/codecs/rt5670.c
index 0af5ddbef1da..8ef467f64f03 100644
--- a/sound/soc/codecs/rt5670.c
+++ b/sound/soc/codecs/rt5670.c
@@ -55,6 +55,7 @@ static const struct reg_sequence init_list[] = {
{ RT5670_PR_BASE + 0x14, 0x9a8a },
{ RT5670_PR_BASE + 0x38, 0x3ba1 },
{ RT5670_PR_BASE + 0x3d, 0x3640 },
+ { 0x8a, 0x0123 },
};
static const struct reg_default rt5670_reg[] = {
@@ -131,7 +132,7 @@ static const struct reg_default rt5670_reg[] = {
{ 0x87, 0x0000 },
{ 0x88, 0x0000 },
{ 0x89, 0x0000 },
- { 0x8a, 0x0000 },
+ { 0x8a, 0x0123 },
{ 0x8b, 0x0000 },
{ 0x8c, 0x0003 },
{ 0x8d, 0x0000 },
--
2.8.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-06-21 18:52 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-06-17 4:08 [PATCH] ASoC: rt5670: patch reg-0x8a Bard Liao
2016-06-17 11:10 ` Mark Brown
2016-06-20 2:10 ` Bard Liao
2016-06-21 18:52 ` Applied "ASoC: rt5670: patch reg-0x8a" to the asoc tree Mark Brown
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).