From: Mark Brown <broonie@kernel.org>
To: Daniel Baluta <daniel.baluta@oss.nxp.com>
Cc: alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.intel.com, lgirdwood@gmail.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
daniel.baluta@gmail.com, linux-imx@nxp.com,
peter.ujfalusi@linux.intel.com,
guennadi.liakhovetski@linux.intel.com,
linux-kernel@vger.kernel.org,
Daniel Baluta <daniel.baluta@nxp.com>,
Paul Olaru <paul.olaru@oss.nxp.com>
Subject: Re: [PATCH 1/5] ASoC: SOF: imx: Add code to manage DSP related clocks
Date: Wed, 17 Nov 2021 12:58:27 +0000 [thread overview]
Message-ID: <YZT8c42cAczfKyMP@sirena.org.uk> (raw)
In-Reply-To: <20211116154613.57122-2-daniel.baluta@oss.nxp.com>
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
On Tue, Nov 16, 2021 at 05:46:09PM +0200, Daniel Baluta wrote:
> From: Daniel Baluta <daniel.baluta@nxp.com>
>
> We need at least 3 clocks in order to power up and access
> DSP core registers found on i.MX8QM, i.MX8QXP and i.MX8MP
> platforms.
This doesn't apply against current code, please check and resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-11-17 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 15:46 [PATCH 0/5] ASoC: SOF: Add PM support for i.MX8/i.MX8X/i.MX8M Daniel Baluta
2021-11-16 15:46 ` [PATCH 1/5] ASoC: SOF: imx: Add code to manage DSP related clocks Daniel Baluta
2021-11-17 12:58 ` Mark Brown [this message]
2021-11-16 15:46 ` [PATCH 2/5] ASoC: SOF: imx8: Add runtime PM / System PM support Daniel Baluta
2021-11-16 15:46 ` [PATCH 3/5] ASoC: SOF: imx8m: " Daniel Baluta
2021-11-16 15:46 ` [PATCH 4/5] ASoC: SOF: imx8m: Implement DSP start Daniel Baluta
2021-11-16 15:46 ` [PATCH 5/5] ASoC: SOF: imx8m: Implement reset callback Daniel Baluta
2021-11-23 0:00 ` [PATCH 0/5] ASoC: SOF: Add PM support for i.MX8/i.MX8X/i.MX8M 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=YZT8c42cAczfKyMP@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=daniel.baluta@oss.nxp.com \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.olaru@oss.nxp.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.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