From: Shunli Wang <shunli.wang@mediatek.com>
To: broonie@kernel.org
Cc: alsa-devel@alsa-project.org, srv_heupstream@mediatek.com,
garlic.tseng@mediatek.com, linux-mediatek@lists.infradead.org,
shunli.wang@mediatek.com, kaichieh.chuang@mediatek.com
Subject: [RESEND PATCH 2/6] ASoC: mediatek: mt8183: add audio afe document
Date: Sat, 26 Jan 2019 15:44:56 +0800 [thread overview]
Message-ID: <1548488700-47792-3-git-send-email-shunli.wang@mediatek.com> (raw)
In-Reply-To: <1548488700-47792-1-git-send-email-shunli.wang@mediatek.com>
Signed-off-by: Shunli Wang <shunli.wang@mediatek.com>
---
.../devicetree/bindings/sound/mt8183-afe-pcm.txt | 36 ++++++++++++++++++++++
1 file changed, 36 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/mt8183-afe-pcm.txt
diff --git a/Documentation/devicetree/bindings/sound/mt8183-afe-pcm.txt b/Documentation/devicetree/bindings/sound/mt8183-afe-pcm.txt
new file mode 100644
index 0000000..396ba38
--- /dev/null
+++ b/Documentation/devicetree/bindings/sound/mt8183-afe-pcm.txt
@@ -0,0 +1,36 @@
+Mediatek AFE PCM controller for mt8183
+
+Required properties:
+- compatible = "mediatek,mt68183-audio";
+- reg: register location and size
+- interrupts: should contain AFE interrupt
+- power-domains: should define the power domain
+- clocks: Must contain an entry for each entry in clock-names
+- clock-names: should have these clock names:
+ "infra_sys_audio_clk",
+ "mtkaif_26m_clk",
+ "top_mux_audio",
+ "top_mux_aud_intbus",
+ "top_sys_pll3_d4",
+ "top_clk26m_clk";
+
+Example:
+
+ afe: mt8183-afe-pcm@11220000 {
+ compatible = "mediatek,mt8183-audio";
+ reg = <0 0x11220000 0 0x1000>;
+ interrupts = <GIC_SPI 161 IRQ_TYPE_LEVEL_LOW>;
+ power-domains = <&scpsys MT8183_POWER_DOMAIN_AUDIO>;
+ clocks = <&infrasys CLK_INFRA_AUDIO>,
+ <&infrasys CLK_INFRA_AUDIO_26M_BCLK>,
+ <&topckgen CLK_TOP_MUX_AUDIO>,
+ <&topckgen CLK_TOP_MUX_AUD_INTBUS>,
+ <&topckgen CLK_TOP_SYSPLL_D2_D4>,
+ <&clk26m>;
+ clock-names = "infra_sys_audio_clk",
+ "mtkaif_26m_clk",
+ "top_mux_audio",
+ "top_mux_aud_intbus",
+ "top_sys_pll_d2_d4",
+ "top_clk26m_clk";
+ };
--
1.9.1
next prev parent reply other threads:[~2019-01-26 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 7:44 [RESEND PATCH 0/6] ASoC: Mediatek: Add support for MT8183 SoC and MT6358 Codec Shunli Wang
2019-01-26 7:44 ` Shunli Wang [this message]
2019-01-26 7:44 ` [RESEND PATCH 3/6] ASoC: mediatek: mt6358: add codec driver Shunli Wang
[not found] ` <1548488700-47792-1-git-send-email-shunli.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-01-26 7:44 ` [RESEND PATCH 1/6] ASoC: mediatek: mt8183: add platform driver Shunli Wang
2019-01-26 7:44 ` [RESEND PATCH 4/6] ASoC: mediatek: mt6358: add codec document Shunli Wang
2019-01-26 7:44 ` [RESEND PATCH 5/6] ASoC: mediatek: mt8183: add mt8183-mt6358 machine driver Shunli Wang
2019-01-26 7:45 ` [RESEND PATCH 6/6] ASoC: mediatek: add document for mt8183-mt6358 Shunli Wang
2019-01-26 12:55 ` [RESEND PATCH 0/6] ASoC: Mediatek: Add support for MT8183 SoC and MT6358 Codec Nicolas Boichat
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=1548488700-47792-3-git-send-email-shunli.wang@mediatek.com \
--to=shunli.wang@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=garlic.tseng@mediatek.com \
--cc=kaichieh.chuang@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=srv_heupstream@mediatek.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