From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ASoC: zte: spdif: correct ZX_SPDIF_CLK_RAT define
Date: Thu, 8 Dec 2016 16:44:15 +0800 [thread overview]
Message-ID: <1481186655-8213-2-git-send-email-shawnguo@kernel.org> (raw)
In-Reply-To: <1481186655-8213-1-git-send-email-shawnguo@kernel.org>
From: Shawn Guo <shawn.guo@linaro.org>
The macro ZX_SPDIF_CLK_RAT should be 2 instead of 4. With this
fix, we can get correct audio output on HDMI through SPDIF interface.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
---
sound/soc/zte/zx-spdif.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/zte/zx-spdif.c b/sound/soc/zte/zx-spdif.c
index 26265ce4caca..9fa6463ce5d7 100644
--- a/sound/soc/zte/zx-spdif.c
+++ b/sound/soc/zte/zx-spdif.c
@@ -71,7 +71,7 @@
#define ZX_VALID_RIGHT_TRACK (2 << 0)
#define ZX_VALID_TRACK_MASK (3 << 0)
-#define ZX_SPDIF_CLK_RAT (4 * 32)
+#define ZX_SPDIF_CLK_RAT (2 * 32)
struct zx_spdif_info {
struct snd_dmaengine_dai_dma_data dma_data;
--
1.9.1
next prev parent reply other threads:[~2016-12-08 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 8:44 [PATCH 1/2] ASoC: zte: spdif and i2s drivers are not zx296702 specific Shawn Guo
2016-12-08 8:44 ` Shawn Guo [this message]
2016-12-08 14:58 ` [PATCH 2/2] ASoC: zte: spdif: correct ZX_SPDIF_CLK_RAT define Jun Nie
2016-12-08 16:55 ` Applied "ASoC: zte: spdif: correct ZX_SPDIF_CLK_RAT define" to the asoc tree Mark Brown
2016-12-08 14:59 ` [PATCH 1/2] ASoC: zte: spdif and i2s drivers are not zx296702 specific Jun Nie
2016-12-08 16:55 ` Applied "ASoC: zte: spdif and i2s drivers are not zx296702 specific" 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=1481186655-8213-2-git-send-email-shawnguo@kernel.org \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).