archive mirror
 help / color / mirror / Atom feed
From: Daniel Baluta <>
	Daniel Baluta <>
Subject: [PATCH v2 0/2] Add code to manage DSP related clocks
Date: Fri,  3 Sep 2021 17:53:38 +0300	[thread overview]
Message-ID: <> (raw)

From: Daniel Baluta <>

This code is based on top of SOF topic/sof-dev branch and we want
to have a review with ALSA and Device Tree communities then it will be merged
to SOF tree and then merged into ALSA tree.

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

Changes since v1:
- used clk bulk API as suggested by mark
Daniel Baluta (2):
  ASoC: SOF: imx: Add code to manage DSP related clocks
  dt-bindings: dsp: fsl: Add DSP optional clocks documentation

 .../devicetree/bindings/dsp/fsl,dsp.yaml      | 33 ++++++++++++++
 sound/soc/sof/imx/imx-common.c                | 44 +++++++++++++++++++
 sound/soc/sof/imx/imx-common.h                | 13 ++++++
 sound/soc/sof/imx/imx8.c                      | 37 ++++++++++++++++
 sound/soc/sof/imx/imx8m.c                     | 34 ++++++++++++++
 5 files changed, 161 insertions(+)


             reply	other threads:[~2021-09-03 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 14:53 Daniel Baluta [this message]
2021-09-03 14:53 ` [PATCH v2 1/2] ASoC: SOF: imx: Add code to manage DSP related clocks Daniel Baluta
2021-09-03 16:06   ` Pierre-Louis Bossart
2021-09-03 14:53 ` [PATCH v2 2/2] dt-bindings: dsp: fsl: Add DSP optional clocks documentation Daniel Baluta
2021-09-03 16:53   ` Rob Herring
2021-09-04 14:50     ` Daniel Baluta
2021-09-07 13:09       ` Rob Herring
2021-09-09 11:20         ` Daniel Baluta
2021-09-09 17:15           ` Rob Herring

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).