From: Daniel Baluta <daniel.baluta@oss.nxp.com>
To: broonie@kernel.org, pierre-louis.bossart@linux.intel.com,
lgirdwood@gmail.com, robh+dt@kernel.org,
devicetree@vger.kernel.org
Cc: ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
shawnguo@kernel.org, kernel@pengutronix.de, festevam@gmail.com,
linux-imx@nxp.com, peter.ujfalusi@linux.intel.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
s-anna@ti.com, Daniel Baluta <daniel.baluta@nxp.com>
Subject: [PATCH 2/2] dt-bindings: dsp: fsl: Add DSP optional clocks documentation
Date: Thu, 2 Sep 2021 15:32:16 +0300 [thread overview]
Message-ID: <20210902123216.787025-3-daniel.baluta@oss.nxp.com> (raw)
In-Reply-To: <20210902123216.787025-1-daniel.baluta@oss.nxp.com>
From: Daniel Baluta <daniel.baluta@nxp.com>
DSP node on the Linux kernel side must also take care of enabling
DAI/DMA related clocks.
By design we choose to manage DAI/DMA clocks from the kernel side because of
the architecture of some i.MX8 boards.
Clocks are handled by a special M4 core which runs a special firmware
called SCFW (System Controler firmware).
This communicates with A cores running Linux via a special Messaging
Unit and implements a custom API which is already implemented by the
Linux kernel i.MX clocks implementation.
Note that these clocks are optional. We can use the DSP without them.
Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
---
.../devicetree/bindings/dsp/fsl,dsp.yaml | 33 +++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/Documentation/devicetree/bindings/dsp/fsl,dsp.yaml b/Documentation/devicetree/bindings/dsp/fsl,dsp.yaml
index 7afc9f2be13a..1453668c0194 100644
--- a/Documentation/devicetree/bindings/dsp/fsl,dsp.yaml
+++ b/Documentation/devicetree/bindings/dsp/fsl,dsp.yaml
@@ -24,16 +24,49 @@ properties:
maxItems: 1
clocks:
+ minItems: 3
items:
- description: ipg clock
- description: ocram clock
- description: core clock
+ - description: esai0 core clock for accessing registers
+ - description: esai0 baud clock
+ - description: esai0 system clock
+ - description: esai0 spba clock required when ESAI is placed in slave mode
+ - description: SAI1 bus clock
+ - description: SAI1 master clock 0
+ - description: SAI1 master clock 1
+ - description: SAI1 master clock 2
+ - description: SAI1 master clock 3
+ - description: SAI3 bus clock
+ - description: SAI3 master clock 0
+ - description: SAI3 master clock 1
+ - description: SAI3 master clock 2
+ - description: SAI3 master clock 3
+ - description: SDMA3 root clock used for accessing registers
+
clock-names:
+ minItems: 3
items:
- const: ipg
- const: ocram
- const: core
+ - const: esai0_core
+ - const: esai0_extal
+ - const: esai0_fsys
+ - const: esai0_spba
+ - const: sai1_bus
+ - const: sai1_mclk0
+ - const: sai1_mclk1
+ - const: sai1_mclk2
+ - const: sai1_mclk3
+ - const: sai3_bus
+ - const: sai3_mclk0
+ - const: sai3_mclk1
+ - const: sai3_mclk2
+ - const: sai3_mclk3
+ - const: smda3_root
power-domains:
description:
--
2.27.0
prev parent reply other threads:[~2021-09-02 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 12:32 [PATCH 0/2] Add code to manage DSP related clocks Daniel Baluta
2021-09-02 12:32 ` [PATCH 1/2] ASoC: SOF: imx: " Daniel Baluta
2021-09-02 13:35 ` Péter Ujfalusi
2021-09-03 15:00 ` Daniel Baluta
2021-09-02 14:49 ` Mark Brown
2021-09-03 14:49 ` Daniel Baluta
2021-09-02 12:32 ` Daniel Baluta [this message]
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=20210902123216.787025-3-daniel.baluta@oss.nxp.com \
--to=daniel.baluta@oss.nxp.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=shawnguo@kernel.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).